Triple
T25388511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton Island Airport |
E631590
|
entity |
| Predicate | primary traffic |
P182201
|
FINISHED |
| Object | tourist 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: tourist flights | Statement: [Hamilton Island Airport, primary traffic, tourist flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primary traffic Context triple: [Hamilton Island Airport, primary traffic, tourist flights]
-
A.
secondaryTraffic
Indicates that there is an additional, indirect, or subordinate flow of traffic associated with a primary traffic stream or event.
-
B.
primaryTraction
Indicates that one entity serves as the main source or means of traction, pulling power, or driving force for another entity or process.
-
C.
primaryTransport
Indicates that one entity serves as the main or most commonly used means of transportation for another entity.
-
D.
primaryRouteType
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
-
E.
primaryRouteThrough
Indicates that one location or path serves as the main or most significant route passing through another location or area.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 21, 2026, 1:47 p.m.