Triple
T36557754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grey Mountains |
E901739
|
entity |
| Predicate | Withered HeathLocation |
P80723
|
FINISHED |
| Object | between Grey Mountains and Iron Hills |
—
|
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: between Grey Mountains and Iron Hills | Statement: [Grey Mountains, Withered HeathLocation, between Grey Mountains and Iron Hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Withered HeathLocation Context triple: [Grey Mountains, Withered HeathLocation, between Grey Mountains and Iron Hills]
-
A.
thornLocation
Indicates the spatial position or placement of a thorn relative to another object or reference point.
-
B.
petrifiedLocation
Indicates that an entity has been turned to stone or fossilized at a specific location.
-
C.
Towheads
Indicates a relationship where entities are characterized by having very light blond hair.
-
D.
hasNearbyWoodland
Indicates that one entity is located close to or in the immediate vicinity of a woodland area associated with another entity.
-
E.
hasMoorland
chosen
Indicates that one entity possesses, contains, or is characterized by moorland terrain or habitat.
- 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.