Triple
T6514621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordzhonikidze |
E148221
|
entity |
| Predicate | currentOfficialStatus |
P28747
|
FINISHED |
| Object | not in official use |
—
|
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: not in official use | Statement: [Ordzhonikidze, currentOfficialStatus, not in official use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentOfficialStatus Context triple: [Ordzhonikidze, currentOfficialStatus, not in official use]
-
A.
coOfficialStatusIn
Indicates that two or more entities share the same official status within a specified context, such as a jurisdiction, organization, or system.
-
B.
governmentStatus
Indicates the type or condition of governance or political authority that an entity currently holds or is subject to.
-
C.
modernStatus
chosen
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
-
D.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
E.
currentStatusSince
Indicates the point in time since which an entity has held its current status or state.
- 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_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. |
Created at: March 27, 2026, 1:44 p.m.