Triple
T38152008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Whaleback |
E952778
|
entity |
| Predicate | nearbyTownPurpose |
P199408
|
FINISHED |
| Object | mining company town for Mount Whaleback 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: mining company town for Mount Whaleback operations | Statement: [Mount Whaleback, nearbyTownPurpose, mining company town for Mount Whaleback operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyTownPurpose Context triple: [Mount Whaleback, nearbyTownPurpose, mining company town for Mount Whaleback operations]
-
A.
nearbyActivityHub
Indicates that one entity is located close enough to another entity that serves as a central hub or focal point for activities or events.
-
B.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
C.
nearbySettlements
Indicates that one settlement is located close to another settlement in geographic space.
-
D.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69ff3705e424819090ad7423ceefa506 |
completed | May 9, 2026, 1:30 p.m. |
Created at: May 3, 2026, 4:21 p.m.