Triple
T35849264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Togarmah |
E1036302
|
entity |
| Predicate | associatedWithPeoplesOrRegions |
P12445
|
FINISHED |
| Object | Phrygians |
E311934
|
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: Phrygians | Statement: [Togarmah, associatedWithPeoplesOrRegions, Phrygians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPeoplesOrRegions Context triple: [Togarmah, associatedWithPeoplesOrRegions, Phrygians]
-
A.
associatedWithContinent
Indicates that an entity has a geographical or contextual connection to a specific continent.
-
B.
associatedWithNationality
Indicates that one entity has a connection or affiliation with the nationality of another entity.
-
C.
hasTerritorialAssociation
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
D.
regionallyAssociatedWith
chosen
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
E.
historicalRegionAssociation
Indicates an association where an entity is or was located in, part of, or otherwise related to a specific historical region.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ae19aa888190a646eec4bf79fd60 |
completed | June 22, 2026, 3:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.