Triple
T38225261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yassıhöyük |
E1012123
|
entity |
| Predicate | historicalPeriodNearbySite |
P203832
|
FINISHED |
| Object | Iron Age |
E12209
|
NE 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: Iron Age | Statement: [Yassıhöyük, historicalPeriodNearbySite, Iron Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodNearbySite Context triple: [Yassıhöyük, historicalPeriodNearbySite, Iron Age]
-
A.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
-
B.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
C.
hasMonumentInPeriod
Indicates that a monument is associated with or existed during a specified time period.
-
D.
historicallyLinkedPlace
Indicates that one place has a significant historical connection or association with another place.
-
E.
hasAdjacentHistoricSite
Indicates that one place is directly next to or very near another place that is recognized as a historic site.
- F. None of above. chosen
Provenance (5 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a02145017b08190bd424cc647c08d3b |
completed | May 11, 2026, 5:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41855349a8819098ff8b0350ebe198 |
completed | June 28, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_6a021338e2b08190980c489ee44c18b3 |
completed | May 11, 2026, 5:34 p.m. |
| PDg | Predicate description generation | batch_6a02144f627c81909ead77e8e6b8f84f |
completed | May 11, 2026, 5:39 p.m. |
Created at: May 3, 2026, 4:30 p.m.