Triple
T26451094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 4 (Melbourne Airport) |
E665348
|
entity |
| Predicate | hasDomesticBaggageClaim |
P30952
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Terminal 4 (Melbourne Airport), hasDomesticBaggageClaim, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomesticBaggageClaim Context triple: [Terminal 4 (Melbourne Airport), hasDomesticBaggageClaim, true]
-
A.
hasBaggageClaim
chosen
Indicates that a location, typically a transportation hub, includes or provides a baggage claim area for retrieving luggage.
-
B.
hasCheckedBaggage
Indicates that an entity is associated with baggage that has been checked in for transport, typically for a trip or flight.
-
C.
hasBaggageCheck
Indicates that an entity provides or is associated with a service or facility for checking in baggage.
-
D.
hasBaggageService
Indicates that an entity provides or supports services related to handling, storing, or managing baggage for others.
-
E.
hasLuggage
Indicates that an entity is carrying, possessing, or associated with one or more pieces of luggage.
- 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_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 12:05 a.m.