Triple
T19639197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aigai |
E471483
|
entity |
| Predicate | hasModernAccessPoint |
P136789
|
FINISHED |
| Object | near Yuntdağ Köseler village |
—
|
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: near Yuntdağ Köseler village | Statement: [Aigai, hasModernAccessPoint, near Yuntdağ Köseler village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernAccessPoint Context triple: [Aigai, hasModernAccessPoint, near Yuntdağ Köseler village]
-
A.
modernAccessPoint
Indicates that an entity serves as a contemporary or up-to-date point of entry, connection, or interaction for accessing another entity or resource.
-
B.
hasModernLocationStatus
Indicates that an entity’s current or contemporary geographic location status is being specified or characterized.
-
C.
hasModernLocation
Indicates that an entity is currently situated in, or corresponds to, a specified modern geographic or administrative location.
-
D.
hasAccessPointFrom
Indicates that an entity can be reached or entered from a specific access point.
-
E.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
- F. None of above. chosen
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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641090c408190b2adb8a6abf1b4c9 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.