Triple
T21266684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ani (ruins) |
E524144
|
entity |
| Predicate | majorExcavationsPeriod |
P135239
|
FINISHED |
| Object | 1892–1917 |
—
|
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: 1892–1917 | Statement: [Ani (ruins), majorExcavationsPeriod, 1892–1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorExcavationsPeriod Context triple: [Ani (ruins), majorExcavationsPeriod, 1892–1917]
-
A.
majorExcavationsDate
chosen
Indicates the date or time period when significant excavation activities were carried out on an entity.
-
B.
majorExcavationEndYear
Indicates the year in which a major excavation activity or project was completed.
-
C.
majorExcavationsBegan
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
D.
hasArchaeologicalRemainsFromPeriod
Indicates that an entity contains or preserves archaeological remains originating from a specified historical period.
-
E.
archaeologicalPhase
Indicates the specific archaeological phase or period to which an object, feature, or context is assigned within a stratigraphic or chronological sequence.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735eca49081908e4f13fcab717c41 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4 p.m.