Triple
T30113451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tell Halaf |
E765347
|
entity |
| Predicate | subsequentExcavations |
P169709
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [Tell Halaf, subsequentExcavations, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentExcavations Context triple: [Tell Halaf, subsequentExcavations, 1929]
-
A.
laterExcavationsStart
Indicates that the start of one excavation occurs after the start of another excavation.
-
B.
archaeologicalExcavations
Indicates that archaeological excavations have been carried out on or are associated with the subject, typically involving systematic digging and recovery of material remains.
-
C.
laterExcavationBy
Indicates that one excavation activity occurred after another excavation activity in time.
-
D.
excavatedAfter
Indicates that one excavation event occurred later in time than another excavation event.
-
E.
hasArchaeologicalExcavationsBy
Indicates that archaeological excavations at a site or location are or were conducted by a specified person, group, or organization.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 7:11 p.m.