Triple
T34730238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brisbane FIR |
E1001187
|
entity |
| Predicate | coversTraffic |
P146573
|
FINISHED |
| Object | domestic 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: domestic flights | Statement: [Brisbane FIR, coversTraffic, domestic flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversTraffic Context triple: [Brisbane FIR, coversTraffic, domestic flights]
-
A.
coversTrafficType
chosen
Indicates that one entity includes, handles, or applies to a specified type or category of traffic.
-
B.
traffics
Indicates engaging in the buying, selling, or illicit trading of someone or something, typically as part of an ongoing commercial or criminal operation.
-
C.
routesTrafficThrough
Indicates that network traffic originating from one entity is directed to pass through another entity as an intermediate path or conduit.
-
D.
carriedTraffic
Indicates that one entity transported, transmitted, or bore the flow of traffic (such as data, vehicles, or signals) for another entity or along a route.
-
E.
supportsTraffic
Indicates that one entity is capable of handling, carrying, or accommodating the flow or volume of traffic associated with another entity.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 3:59 p.m.