Triple
T3607857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crusades |
E76415
|
entity |
| Predicate | endApproximateDate |
P35259
|
FINISHED |
| Object | late 13th century |
—
|
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: late 13th century | Statement: [Crusades, endApproximateDate, late 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endApproximateDate Context triple: [Crusades, endApproximateDate, late 13th century]
-
A.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
B.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
D.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
E.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc228e24481909ae6a1e4ad796917 |
completed | March 8, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.