Triple
T6862420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEL |
E158312
|
entity |
| Predicate | terminal4Usage |
P74166
|
FINISHED |
| Object | low-cost carriers |
—
|
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: low-cost carriers | Statement: [MEL, terminal4Usage, low-cost carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminal4Usage Context triple: [MEL, terminal4Usage, low-cost carriers]
-
A.
terminal2Usage
Indicates that an entity makes use of or operates through a second terminal or secondary terminal interface.
-
B.
terminal3Use
Indicates that an entity makes use of or operates from terminal 3 (such as a specific terminal in a facility, station, or airport).
-
C.
TerminalEUsedFor
Indicates that a terminal E is used for a particular purpose, function, or activity.
-
D.
terminal4Operator
Indicates that an entity operates or manages the facilities, services, or activities associated with Terminal 4 of a larger transportation hub.
-
E.
terminalFunction
Indicates that an entity serves as an endpoint or final functional unit within a larger structure, process, or system.
- F. None of above. chosen
Provenance (4 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_69c68830cdbc8190a8301c7a9d9f651a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6da3b5510819093c5893ea92ac025 |
completed | March 27, 2026, 7:27 p.m. |
Created at: March 27, 2026, 2:21 p.m.