Triple
T1370988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne Airport |
E30111
|
entity |
| Predicate | terminal2PrimaryUse |
P10000
|
FINISHED |
| Object | international flights |
—
|
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: international flights | Statement: [Melbourne Airport, terminal2PrimaryUse, international flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminal2PrimaryUse Context triple: [Melbourne Airport, terminal2PrimaryUse, international flights]
-
A.
usedTerminal
Indicates that an entity made use of or interacted with a particular terminal or endpoint device.
-
B.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
C.
usedPrimarilyIn
chosen
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
D.
primaryDeviceCategory
Indicates the main type or class of device associated with an entity or event, distinguishing it from other possible device categories.
-
E.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d7b6008190bc0303b56959ba56 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.