Triple
T10412805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LH |
E245433
|
entity |
| Predicate | usedAsPrefixFor |
P66290
|
FINISHED |
| Object | Lufthansa 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: Lufthansa flight numbers | Statement: [LH, usedAsPrefixFor, Lufthansa flight numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsPrefixFor Context triple: [LH, usedAsPrefixFor, Lufthansa flight numbers]
-
A.
usedAsParentFor
Indicates that one entity functions as the parent or container for another entity within a hierarchical or structural relationship.
-
B.
usedAsNameSourceFor
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
-
C.
usedAsSuffixTo
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
namespacePrefix
chosen
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0e17f081908fb16425f65e5808 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.