Triple
T8690150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule XIV |
E206264
|
entity |
| Predicate | workDateApproximate |
P877
|
FINISHED |
| Object | 1620s |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1620s | Statement: [Rule XIV, workDateApproximate, 1620s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workDateApproximate Context triple: [Rule XIV, workDateApproximate, 1620s]
-
A.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
commutationDate
Indicates the date on which a sentence or penalty is formally reduced, altered, or commuted.
-
C.
employedApproximately
Indicates that one entity employs another in a manner where the number, duration, or extent of employment is approximate rather than exact.
-
D.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
E.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5734602c81909a0687e00f4a4a26 |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.