Triple
T6971924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roof of the World |
E161616
|
entity |
| Predicate | hasAlternativeEpithetForSameRegion |
P11942
|
FINISHED |
| Object | Third Pole |
—
|
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: Third Pole | Statement: [Roof of the World, hasAlternativeEpithetForSameRegion, Third Pole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeEpithetForSameRegion Context triple: [Roof of the World, hasAlternativeEpithetForSameRegion, Third Pole]
-
A.
hasAlternativeNameForSameCity
Indicates that one city name is an alternative or variant name referring to the same city as another name.
-
B.
isRegionalAlternativeTo
Indicates that one entity serves as a counterpart or substitute for another within a specific geographic region or local context.
-
C.
regionalVariantOf
chosen
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
-
D.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
E.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
- 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db398f10819096d34b179ccb20d5 |
completed | March 27, 2026, 7:32 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.