Triple
T23770788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | URMO |
E587519
|
entity |
| Predicate | isUniqueIdentifierFor |
P3732
|
FINISHED |
| Object | Beslan Airport |
—
|
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: Beslan Airport | Statement: [URMO, isUniqueIdentifierFor, Beslan Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUniqueIdentifierFor Context triple: [URMO, isUniqueIdentifierFor, Beslan Airport]
-
A.
isUniqueTo
Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
-
B.
isUniqueWithinSystem
Indicates that an entity exists only once and has no duplicates within the defined system or scope.
-
C.
isUniqueWithinStandard
Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
-
D.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
E.
isNonUniqueGlobally
Indicates that the referenced item is not guaranteed to be unique across the entire global scope or system.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c465d7948190a4381e39f792a7b4 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:15 p.m.