Triple
T25388515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton Island Airport |
E631590
|
entity |
| Predicate | operator type |
P21524
|
FINISHED |
| Object | private |
—
|
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: private | Statement: [Hamilton Island Airport, operator type, private]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operator type Context triple: [Hamilton Island Airport, operator type, private]
-
A.
operator
Indicates that one entity functions as the operator (controller or handler) of another entity, such as a system, device, or process.
-
B.
operatorBase
Indicates that one entity serves as the primary or foundational operator for another entity or operation.
-
C.
typicalOperatorType
chosen
Indicates the usual or most common type or category of operator associated with a given entity or context.
-
D.
operatorVariant
Indicates a relationship where one operator is an alternative or modified form of another, typically differing in implementation, configuration, or usage while serving a related function.
-
E.
operatorSymbol
Indicates the symbolic notation used to represent an operator in an expression or formal system.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 21, 2026, 1:47 p.m.