Triple
T7309266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amri |
E168050
|
entity |
| Predicate | chronologyEnd |
P76220
|
FINISHED |
| Object | c. 2600 BCE |
—
|
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: c. 2600 BCE | Statement: [Amri, chronologyEnd, c. 2600 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyEnd Context triple: [Amri, chronologyEnd, c. 2600 BCE]
-
A.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
B.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
C.
chronologyEstablishedBy
Indicates that the temporal order or dating of events, objects, or periods is determined or defined by a specified source, method, or authority.
-
D.
chronologyStartEvent
Indicates the event that marks the beginning or initial point in a chronological sequence or timeline.
-
E.
chronologyPrevious
Indicates that one event, item, or state occurs directly before another in a chronological sequence.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebdbd6f481908e69e53dab452656 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 3:01 p.m.