Triple
T28054388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telnet Status Option |
E708919
|
entity |
| Predicate | hasIACSequencePrefix |
P66954
|
FINISHED |
| Object | 255 |
—
|
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: 255 | Statement: [Telnet Status Option, hasIACSequencePrefix, 255]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIACSequencePrefix Context triple: [Telnet Status Option, hasIACSequencePrefix, 255]
-
A.
hasInstructionPrefix
Indicates that one entity provides an initial segment or starting portion that serves as the instruction prefix for another entity.
-
B.
hasICAOSuccessorCode
Indicates that one ICAO airport code has been replaced or superseded by another ICAO airport code.
-
C.
hasPrefix
chosen
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
D.
hasStationCodePrefix
Indicates that one entity’s station code begins with the prefix specified by the other entity.
-
E.
isSequence
Indicates that one entity is an ordered list or succession of elements arranged in a specific, meaningful order.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fdba3688190bc5e0e7b73e46089 |
completed | May 2, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:35 p.m.