Triple
T10522393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Watchung Mountain |
E248206
|
entity |
| Predicate | relativePositionInRange |
P23578
|
FINISHED |
| Object | third ridge |
—
|
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: third ridge | Statement: [Third Watchung Mountain, relativePositionInRange, third ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionInRange Context triple: [Third Watchung Mountain, relativePositionInRange, third ridge]
-
A.
positionInRange
Indicates that an entity’s position lies within a specified numerical or spatial range.
-
B.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
D.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
E.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509e0907481908807dd99980cba1f |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:29 p.m.