Triple
T6514620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordzhonikidze |
E148221
|
entity |
| Predicate | toponymStatus |
P71313
|
FINISHED |
| Object | obsolete |
—
|
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: obsolete | Statement: [Ordzhonikidze, toponymStatus, obsolete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toponymStatus Context triple: [Ordzhonikidze, toponymStatus, obsolete]
-
A.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
B.
hasToponymicUse
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
-
C.
isToponymic
Indicates that something is related to or derived from a place name (a toponym).
-
D.
exonymStatus
Indicates the status or classification of a name used in one language to refer to a place, people, or entity known by a different name in its own language.
-
E.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
- F. None of above. chosen
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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0bea808190aebc2905fb53eeba |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:44 p.m.