Triple
T33920703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakapınar |
E869598
|
entity |
| Predicate | nearbyAncientNameVariant |
P196516
|
FINISHED |
| Object | Mopsuhestia |
—
|
NE NERFINISHED |
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: Mopsuhestia | Statement: [Yakapınar, nearbyAncientNameVariant, Mopsuhestia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAncientNameVariant Context triple: [Yakapınar, nearbyAncientNameVariant, Mopsuhestia]
-
A.
nearbyAncientName
chosen
Indicates that one entity has an ancient name that was historically used for a place or feature located near the other entity.
-
B.
nearAncientRegion
Indicates that one entity is located close to, or in the immediate vicinity of, a specified ancient geographical region.
-
C.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
D.
nearbyRomanTown
Indicates that one location is geographically close to a town that existed during the Roman period.
-
E.
nearbyArchaeologicalCulture
Indicates that one archaeological culture is geographically close to another archaeological culture.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 1, 2026, 1:49 a.m.