Triple
T2855154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston, Rhode Island |
E63181
|
entity |
| Predicate | distanceToAtlanticCoast |
P15760
|
FINISHED |
| Object | approximately 5–7 miles 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 5–7 miles inland | Statement: [Kingston, Rhode Island, distanceToAtlanticCoast, approximately 5–7 miles inland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAtlanticCoast Context triple: [Kingston, Rhode Island, distanceToAtlanticCoast, approximately 5–7 miles inland]
-
A.
distanceFromCoast
chosen
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
B.
distanceToPacificOcean
Indicates the physical distance between a given location or entity and the Pacific Ocean.
-
C.
distanceFromMainland
Indicates the measured spatial separation between a location and the nearest point on the mainland.
-
D.
distanceFromBoston
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
E.
distanceToPennsylvaniaBorder
Indicates the measured distance between a given location and the border of Pennsylvania.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf60852c8190b66c8719c63a723e |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.