Triple
T31013245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarabulus |
E790260
|
entity |
| Predicate | operationEuphratesShieldStartDate |
P200493
|
FINISHED |
| Object | 2016-08-24 |
—
|
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-08-24 | Statement: [Jarabulus, operationEuphratesShieldStartDate, 2016-08-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationEuphratesShieldStartDate Context triple: [Jarabulus, operationEuphratesShieldStartDate, 2016-08-24]
-
A.
eraOfOperation
Indicates the time period or span of years during which an entity was active or in operation.
-
B.
autonomyPeriodStart
Indicates the point in time when an entity’s autonomous operation or independent control begins.
-
C.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
-
D.
RAEpoch
Indicates the specific epoch or time period during which a right ascension (RA) value is defined or measured.
-
E.
shareHistoricalUnionPeriod
Indicates that two entities were part of the same political or administrative union during an overlapping historical time period.
- F. None of above. chosen
Provenance (4 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69ff90b5b98881909620033d78e4a9b8 |
completed | May 9, 2026, 7:53 p.m. |
Created at: April 29, 2026, 8:57 p.m.