Triple
T36856470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Meharry |
E910807
|
entity |
| Predicate | nearestMajorTownRegion |
P186589
|
FINISHED |
| Object | Pilbara mining towns |
—
|
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: Pilbara mining towns | Statement: [Mount Meharry, nearestMajorTownRegion, Pilbara mining towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorTownRegion Context triple: [Mount Meharry, nearestMajorTownRegion, Pilbara mining towns]
-
A.
nearestMajorTowns
Indicates that one or more major towns are the closest significant urban centers to a given location or entity.
-
B.
majorTownInRegion
Indicates that a town is one of the principal or most significant towns within a specified region.
-
C.
nearestSuburbOrTown
Indicates that one place is the geographically closest suburb or town to another specified location.
-
D.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
E.
nearestMajorState
Indicates the relationship where a given location is associated with the closest major state to it, typically by geographic distance.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.