Triple
T8658492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Schiehallion |
E205484
|
entity |
| Predicate | positionWithinFeature |
P12261
|
FINISHED |
| Object | eastern section of Schiehallion |
—
|
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: eastern section of Schiehallion | Statement: [East Schiehallion, positionWithinFeature, eastern section of Schiehallion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinFeature Context triple: [East Schiehallion, positionWithinFeature, eastern section of Schiehallion]
-
A.
positionWithinComplex
Indicates that one entity is located inside or forms a component part of a larger complex or compound structure.
-
B.
withinFeature
chosen
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
C.
positionInField
Indicates the specific role, location, or functional placement an entity occupies within a defined field, domain, or area of activity.
-
D.
positionInRange
Indicates that an entity’s position lies within a specified numerical or spatial range.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc486d576081908ad28749c7971432 |
completed | March 31, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:30 p.m.