Triple
T22144840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bartholomew I of Constantinople |
E547257
|
entity |
| Predicate | dateOfEventOrganized |
P140492
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Bartholomew I of Constantinople, dateOfEventOrganized, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfEventOrganized Context triple: [Bartholomew I of Constantinople, dateOfEventOrganized, 2016]
-
A.
eventStartDateOrganized
Indicates the date on which an event is formally scheduled or organized to begin.
-
B.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
C.
dateOfEventCommand
Indicates a command or instruction that specifies or requests the date on which an event occurs.
-
D.
mainEventDate
chosen
Indicates the primary or most significant date on which the referenced event occurs or is scheduled to occur.
-
E.
organisedDuring
Indicates that an organizing action or arrangement took place within the time span of a specified event or period.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129efd52c8190ab0acff5bbfc0d77 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.