Triple
T17345665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Isa Airport |
E421680
|
entity |
| Predicate | primaryServiceIndustry |
P101656
|
FINISHED |
| Object | mining |
—
|
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: mining | Statement: [Mount Isa Airport, primaryServiceIndustry, mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryServiceIndustry Context triple: [Mount Isa Airport, primaryServiceIndustry, mining]
-
A.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
B.
primarySectorActivity
chosen
Indicates the main industry or sector in which an entity primarily conducts its activities or operations.
-
C.
primaryTrade
Indicates that the referenced activity or exchange is the main or most significant trade relationship associated with the entities involved.
-
D.
economicSectorDominant
Indicates that one economic sector holds a leading or controlling position relative to others in terms of influence, output, or importance.
-
E.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a286d34819080c5148c220fd5a1 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.