Triple
T405442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sankaty Head Light |
E9372
|
entity |
| Predicate | relocationDistance |
P7750
|
FINISHED |
| Object | approximately 400 feet inland |
—
|
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: approximately 400 feet inland | Statement: [Sankaty Head Light, relocationDistance, approximately 400 feet inland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationDistance Context triple: [Sankaty Head Light, relocationDistance, approximately 400 feet inland]
-
A.
distance
chosen
Indicates the spatial separation or length between two points, objects, or locations.
-
B.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
C.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
D.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
-
E.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca37fe881909802126952dfdd59 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.