Triple
T16960991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO airport code system |
E411425
|
entity |
| Predicate | lastLettersIndicate |
P108177
|
FINISHED |
| Object | specific aerodrome |
—
|
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: specific aerodrome | Statement: [ICAO airport code system, lastLettersIndicate, specific aerodrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastLettersIndicate Context triple: [ICAO airport code system, lastLettersIndicate, specific aerodrome]
-
A.
lastLetter
Indicates that one entity is the final character in the written or spelled form of another entity.
-
B.
lastStanzaLetter
Indicates that a given letter is the final letter of the last stanza in a text or poem.
-
C.
hasLastThreeLettersMeaning
Indicates that the last three letters of one entity (typically a word or string) together form a meaningful unit or have a specific semantic significance.
-
D.
lastThreeCharacters
chosen
Indicates that one entity consists of, or specifies, the final three characters of another entity’s string representation.
-
E.
lastWordsTo
Indicates that one entity spoke their final words or message directed specifically to another entity.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0209a9081909d9c62456bc16e14 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.