Triple
T26200105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amri culture |
E655205
|
entity |
| Predicate | hasChronologyEnd |
P76220
|
FINISHED |
| Object | circa 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: circa 2600 BCE | Statement: [Amri culture, hasChronologyEnd, circa 2600 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChronologyEnd Context triple: [Amri culture, hasChronologyEnd, circa 2600 BCE]
-
A.
chronologyEnd
chosen
Indicates that one event, state, or time interval marks the ending point or conclusion of another in a temporal sequence.
-
B.
hasTemporalEnd
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
C.
hasChronologyStatus
Indicates the temporal or sequential status of something within a chronology, such as whether its position or order in time is known, uncertain, or otherwise classified.
-
D.
hasChronologyItem
Indicates that something is associated with a specific item or entry within an ordered chronological sequence or timeline.
-
E.
chronologicalCoverageEnd
Indicates the point in time at which the temporal or chronological span of something (such as a resource, event, or record) comes to an end.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 26, 2026, 8:48 p.m.