Triple
T26200104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amri culture |
E655205
|
entity |
| Predicate | hasChronologyStart |
P76219
|
FINISHED |
| Object | circa 3600 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 3600 BCE | Statement: [Amri culture, hasChronologyStart, circa 3600 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChronologyStart Context triple: [Amri culture, hasChronologyStart, circa 3600 BCE]
-
A.
chronologyStart
chosen
Indicates the point in time at which a sequence, event, or temporal record begins.
-
B.
hasChronologyItem
Indicates that something is associated with a specific item or entry within an ordered chronological sequence or timeline.
-
C.
hasApproxGregorianStart
Indicates that an entity has an associated start date expressed as an approximate value in the Gregorian calendar.
-
D.
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.
-
E.
chronologyStartEvent
Indicates the event that marks the beginning or initial point in a chronological sequence or timeline.
- 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_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 8:48 p.m.