Triple
T33112707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annúminas |
E847371
|
entity |
| Predicate | hasCounterpartCity |
P919
|
FINISHED |
| Object | Minas Tirith |
E199107
|
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: Minas Tirith | Statement: [Annúminas, hasCounterpartCity, Minas Tirith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCounterpartCity Context triple: [Annúminas, hasCounterpartCity, Minas Tirith]
-
A.
oppositeCityCountry
Indicates that a city and a country are located on opposite sides of the world or in geographically opposing regions relative to each other.
-
B.
hasTwinTown
chosen
Indicates that two towns or cities are officially paired in a twinning relationship, typically for cultural, social, or economic exchange.
-
C.
isNeighboringCityOf
Indicates that one city is geographically adjacent to or directly borders another city.
-
D.
hasCounterpartName
Indicates that an entity has an alternative or corresponding name used as its counterpart in another context, system, or representation.
-
E.
sisterCityCountry
Indicates that a city has an official sister-city relationship with a city located in the specified 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34f036b9748190a04d852afc32832e |
completed | June 19, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:27 a.m.