Triple
T36856334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shire of Ashburton |
E910804
|
entity |
| Predicate | containsTownSupportingIndustry |
P60143
|
FINISHED |
| Object | Paraburdoo |
—
|
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: Paraburdoo | Statement: [Shire of Ashburton, containsTownSupportingIndustry, Paraburdoo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTownSupportingIndustry Context triple: [Shire of Ashburton, containsTownSupportingIndustry, Paraburdoo]
-
A.
hasIndustrialTown
chosen
Indicates that an entity possesses or is associated with a town characterized primarily by industrial activities or facilities.
-
B.
hasSmallTownIndustry
Indicates that a small town possesses or supports a particular type of industry or industrial activity.
-
C.
containsIndustrialAreas
Indicates that one entity includes or encompasses industrial areas within its boundaries or scope.
-
D.
hasIndustrialSector
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
E.
hasIndustrialPark
Indicates that a location or entity possesses or contains an industrial park within its area or jurisdiction.
- 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_6a0141fceb908190863778741bd4487d |
completed | May 11, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_6a0141a9628c819090c0b24ce052a2fb |
completed | May 11, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:13 p.m.