Triple
T37517639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypaepa |
E932677
|
entity |
| Predicate | countryOfModernSite |
P89660
|
FINISHED |
| Object | Turkey |
E1845
|
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: Turkey | Statement: [Hypaepa, countryOfModernSite, Turkey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfModernSite Context triple: [Hypaepa, countryOfModernSite, Turkey]
-
A.
isLocatedInPresentDayCountry
chosen
Indicates that an entity’s location is specified in terms of the modern, currently recognized country that encompasses it.
-
B.
countryOfUNESCOProperty
Indicates the country that has jurisdiction over or is officially associated with a given UNESCO property.
-
C.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
D.
countryAtExcavationTime
Indicates that a specified location or site was within the borders or jurisdiction of a particular country at the time the excavation took place.
-
E.
emergedInPresentDayCountry
Indicates that something (such as a group, movement, or phenomenon) originally arose or came into existence within the geographic area of a specified modern-day country.
- F. None of above.
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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a036f0569cc8190a8ac7f4e07145d15 |
completed | May 12, 2026, 6:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409eff47c48190875486c15b03f08d |
completed | June 28, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_6a036c42cf2481908760c7d48b9fc001 |
completed | May 12, 2026, 6:06 p.m. |
Created at: May 3, 2026, 4:17 p.m.