Triple
T35766298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tectosages |
E1034023
|
entity |
| Predicate | capitalNear |
P41518
|
FINISHED |
| Object | Ancyra |
—
|
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: Ancyra | Statement: [Tectosages, capitalNear, Ancyra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalNear Context triple: [Tectosages, capitalNear, Ancyra]
-
A.
capitalOrMajorCenter
Indicates that a location serves as a capital city or a primary major center (political, economic, or cultural hub) for a larger region or entity.
-
B.
capitalPossiblyAt
Indicates a possible or uncertain capital relationship, where one location may be the capital of another but this is not definitively established.
-
C.
capitalLikeCity
Indicates that a capital city shares similar characteristics or status to a particular city.
-
D.
regionCapitalNearby
chosen
Indicates that a capital city of a region is located close to the referenced place or entity.
-
E.
capitalApproximateLocation
Indicates that the relationship specifies an approximate or general geographic location of a capital city rather than its precise coordinates.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:06 p.m.