Triple
T5474586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tell es-Sultan |
E122917
|
entity |
| Predicate | KenyonExcavationPeriod |
P28985
|
FINISHED |
| Object | 1952–1958 |
—
|
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: 1952–1958 | Statement: [Tell es-Sultan, KenyonExcavationPeriod, 1952–1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KenyonExcavationPeriod Context triple: [Tell es-Sultan, KenyonExcavationPeriod, 1952–1958]
-
A.
hasArchaeologicalRemainsFromPeriod
Indicates that an entity contains or preserves archaeological remains originating from a specified historical period.
-
B.
archaeologicallyExploredSince
chosen
Indicates that a place or site has been subject to archaeological exploration starting from a specified point in time.
-
C.
archaeologicalPhase
Indicates the specific archaeological phase or period to which an object, feature, or context is assigned within a stratigraphic or chronological sequence.
-
D.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
E.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9232ded08190b4142e604319b2ba |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.