Triple
T25121494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tell ed-Duweir |
E629277
|
entity |
| Predicate | firstMajorExcavationStart |
P7651
|
FINISHED |
| Object | 1932 |
—
|
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: 1932 | Statement: [Tell ed-Duweir, firstMajorExcavationStart, 1932]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorExcavationStart Context triple: [Tell ed-Duweir, firstMajorExcavationStart, 1932]
-
A.
firstExcavationYear
Indicates the calendar year in which an excavation activity at a given site or object was first carried out.
-
B.
majorExcavationsBegan
chosen
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
C.
laterExcavationsStart
Indicates that the start of one excavation occurs after the start of another excavation.
-
D.
majorExcavationsDate
Indicates the date or time period when significant excavation activities were carried out on an entity.
-
E.
firstScientificExcavationsEndDate
Indicates the date on which the first scientific excavations at a given site or for a given subject were completed.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 18, 2026, 6:28 a.m.