Triple
T26451102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 4 (Melbourne Airport) |
E665348
|
entity |
| Predicate | hasDepartureLevel |
P38072
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Terminal 4 (Melbourne Airport), hasDepartureLevel, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepartureLevel Context triple: [Terminal 4 (Melbourne Airport), hasDepartureLevel, yes]
-
A.
hasDepartureTo
Indicates that a departure event originates from one place and is directed toward a specific destination.
-
B.
hasDepartureSide
Indicates the side or direction from which an entity departs or leaves a location.
-
C.
hasArrivalLevel
Indicates that an entity arrives at or is associated with a specific level, floor, or tier within a larger structure or system.
-
D.
hasDepartureArea
chosen
Indicates that something (such as a trip, route, or transport service) has a specific area or location from which it departs.
-
E.
hasDepartureEnd
Indicates that an entity marks the endpoint or final location of a departure event or journey.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 12:05 a.m.