Triple
T35607237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Mountain region (unspecified jurisdiction) |
E1028925
|
entity |
| Predicate | hasCoreAreaNamed |
P185210
|
FINISHED |
| Object | Black Mountain |
E80143
|
NE 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: Black Mountain | Statement: [Black Mountain region (unspecified jurisdiction), hasCoreAreaNamed, Black Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreAreaNamed Context triple: [Black Mountain region (unspecified jurisdiction), hasCoreAreaNamed, Black Mountain]
-
A.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
B.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
C.
hasAreaName
chosen
Indicates that an entity is associated with a specific named geographic or administrative area.
-
D.
hasCurrentCoreCityName
Indicates that an entity is associated with its present or officially recognized core city name.
-
E.
isCoreZone
Indicates that something belongs to, or is located within, the central or most important zone of a defined area or system.
- F. None of above.
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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a394d1606dc8190b251bbc728bcf3e9 |
completed | June 22, 2026, 2:56 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.