Triple
T22279471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LIS Terminal 2 |
E550691
|
entity |
| Predicate | hasTypeOfOperation |
P1137
|
FINISHED |
| Object | short-haul operations |
—
|
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: short-haul operations | Statement: [LIS Terminal 2, hasTypeOfOperation, short-haul operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfOperation Context triple: [LIS Terminal 2, hasTypeOfOperation, short-haul operations]
-
A.
hasOperationType
chosen
Indicates the specific kind or category of operation associated with an entity or process.
-
B.
typeOfOperation
Indicates the specific kind or category of operation being performed or referenced in a given context.
-
C.
handlesOperationType
Indicates that an entity is responsible for processing or managing a specific type or category of operation.
-
D.
hasTypeOfInstruction
Indicates that one entity specifies, assigns, or is associated with a particular type or category of instruction for another entity.
-
E.
hasBinaryOperation
Indicates that there exists a binary operation defined on the related entity or between the related entities, combining two inputs to produce a single output.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14eaa8cec819081c2ad031154ebe7 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.