Triple
T36557753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grey Mountains |
E901739
|
entity |
| Predicate | hadSubregion |
P144195
|
FINISHED |
| Object | Withered Heath |
—
|
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: Withered Heath | Statement: [Grey Mountains, hadSubregion, Withered Heath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSubregion Context triple: [Grey Mountains, hadSubregion, Withered Heath]
-
A.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
B.
hasSubregionRelationWith
chosen
Indicates a relationship where one region is a subregion or contained part of another region.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
hasSubregionStatus
Indicates that one region holds an official or defined status as a subregion within a larger geographic or administrative area.
-
E.
subregionName
Indicates that one region is identified by a specific name used for a smaller or subordinate geographic or administrative area within a larger region.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.