Triple
T36856299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paraburdoo Airport |
E910803
|
entity |
| Predicate | serves industry |
P112563
|
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: [Paraburdoo Airport, serves industry, mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serves industry Context triple: [Paraburdoo Airport, serves industry, mining]
-
A.
supportedIndustry
chosen
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
-
B.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
C.
overseesIndustry
Indicates that one entity has supervisory or regulatory authority over the activities, operations, or standards of a particular industry.
-
D.
industryStart
Indicates the point in time or event at which an industry, industrial activity, or industrial era begins.
-
E.
servesIndustrialRegion
Indicates that an entity provides services or support to an industrial region, fulfilling functional or operational needs of that area.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: May 3, 2026, 4:13 p.m.