Triple
T34730244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brisbane FIR |
E1001187
|
entity |
| Predicate | hasServiceUnit |
P201264
|
FINISHED |
| Object | Brisbane Area Control Centre |
—
|
NE NERFINISHED |
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: Brisbane Area Control Centre | Statement: [Brisbane FIR, hasServiceUnit, Brisbane Area Control Centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceUnit Context triple: [Brisbane FIR, hasServiceUnit, Brisbane Area Control Centre]
-
A.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
B.
hasServiceModule
Indicates that an entity is equipped with, or associated with, a specific service module that provides supporting or auxiliary functions.
-
C.
hasServiceFrom
Indicates that one entity receives or benefits from a service provided by another entity.
-
D.
hasUnitFeature
Indicates that something possesses a specific unit-related characteristic or attribute, such as a measurable feature expressed in defined units.
-
E.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffe23081408190a121d901dbce1403 |
completed | May 10, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ffe18aed348190912a5996b2da728b |
completed | May 10, 2026, 1:38 a.m. |
| PDg | Predicate description generation | batch_69ffe22f453c81909867ee2d2047636f |
completed | May 10, 2026, 1:41 a.m. |
Created at: May 3, 2026, 3:59 p.m.