Triple
T26153589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Beacon Mountain |
E659893
|
entity |
| Predicate | relativePositionTo |
P23578
|
FINISHED |
| Object | south of North Beacon Mountain |
—
|
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: south of North Beacon Mountain | Statement: [South Beacon Mountain, relativePositionTo, south of North Beacon Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionTo Context triple: [South Beacon Mountain, relativePositionTo, south of North Beacon Mountain]
-
A.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
B.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
C.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
D.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
E.
relativePositionInGroup
Indicates the spatial or ordered placement of an entity within a defined group relative to the other members of that group.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 26, 2026, 8:26 p.m.