Triple
T36856342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shire of Ashburton |
E910804
|
entity |
| Predicate | containsResourceProject |
P108759
|
FINISHED |
| Object | iron ore mining operations |
—
|
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: iron ore mining operations | Statement: [Shire of Ashburton, containsResourceProject, iron ore mining operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsResourceProject Context triple: [Shire of Ashburton, containsResourceProject, iron ore mining operations]
-
A.
associatedWithResourceProjects
chosen
Indicates a relationship where an entity is linked or connected to specific resource-related projects, such as their development, management, or use.
-
B.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
C.
hasSubproject
Indicates that a project includes another project as a subordinate or component part within its overall structure.
-
D.
includesResources
Indicates that one entity contains, encompasses, or makes available specific resources as part of its composition or offering.
-
E.
hasExtensionProject
Indicates that an entity is associated with or participates in a specific extension project.
- 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_6a0143a4ab3c8190a240b0facfe130a9 |
completed | May 11, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_6a01426b2d4481908654bfa4a02c457d |
completed | May 11, 2026, 2:43 a.m. |
Created at: May 3, 2026, 4:13 p.m.