Triple
T30113413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zincirli |
E765346
|
entity |
| Predicate | firstMajorExcavationsEndDate |
P135239
|
FINISHED |
| Object | 1902 |
—
|
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: 1902 | Statement: [Zincirli, firstMajorExcavationsEndDate, 1902]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorExcavationsEndDate Context triple: [Zincirli, firstMajorExcavationsEndDate, 1902]
-
A.
firstScientificExcavationsEndDate
Indicates the date on which the first scientific excavations at a given site or for a given subject were completed.
-
B.
firstExcavationYear
Indicates the calendar year in which an excavation activity at a given site or object was first carried out.
-
C.
majorExcavationEndYear
Indicates the year in which a major excavation activity or project was completed.
-
D.
majorExcavationsDate
chosen
Indicates the date or time period when significant excavation activities were carried out on an entity.
-
E.
majorExcavationsBegan
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a019d1407588190b3b9b83fca2e61fe |
completed | May 11, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a019c760e3081909cfe9c0603727e48 |
completed | May 11, 2026, 9:08 a.m. |
Created at: April 29, 2026, 7:11 p.m.