Triple
T3956121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UL |
E84980
|
entity |
| Predicate | appearsAsPrefixIn |
P27718
|
FINISHED |
| Object | SriLankan Airlines flight numbers |
—
|
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: SriLankan Airlines flight numbers | Statement: [UL, appearsAsPrefixIn, SriLankan Airlines flight numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAsPrefixIn Context triple: [UL, appearsAsPrefixIn, SriLankan Airlines flight numbers]
-
A.
appearsBefore
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
-
B.
hasPrepositionalPrefix
Indicates that one entity functions as a prepositional prefix attached to or modifying another entity.
-
C.
hasPrefixMeaning
chosen
Indicates that one entity serves as a semantic prefix of another, contributing a specific meaning to the start of the second entity.
-
D.
preambleBeginsWith
Indicates that the preamble of a document or text starts with a specified substring, phrase, or content.
-
E.
precedesLetter
Indicates that one letter comes immediately before another letter in a specified ordering, such as the alphabet or a given sequence.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:30 p.m.