Triple
T25288943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamrun |
E634025
|
entity |
| Predicate | supersededByToponym |
P64305
|
FINISHED |
| Object | Bandar Abbas |
—
|
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: Bandar Abbas | Statement: [Gamrun, supersededByToponym, Bandar Abbas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supersededByToponym Context triple: [Gamrun, supersededByToponym, Bandar Abbas]
-
A.
replacedByToponym
chosen
Indicates that one name or designation has been superseded and is now represented or referred to by a toponym (a place-based name).
-
B.
hasToponymicDerivatives
Indicates that a name or term serves as the source from which related place-based or toponymic names are derived.
-
C.
isToponymOf
Indicates that one entity is a place name (toponym) that refers to the location represented by the other entity.
-
D.
usedAsToponymicBy
Indicates that one entity is employed as a place-based surname or name-forming element for another entity.
-
E.
legacyToponym
Indicates that one place name is an older or former name historically used to refer to the same geographic entity as another place name.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 1:21 p.m.