Triple
T10296115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pembroke, New Hampshire |
E241491
|
entity |
| Predicate | distanceToStateCapital_km |
P28400
|
FINISHED |
| Object | approximately 8 |
—
|
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 8 | Statement: [Pembroke, New Hampshire, distanceToStateCapital_km, approximately 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToStateCapital_km Context triple: [Pembroke, New Hampshire, distanceToStateCapital_km, approximately 8]
-
A.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
hasCountyCapitalDistance
Indicates a distance relationship specifying how far a county is from its capital.
-
C.
distanceToDepartmentCapital
Indicates the measured distance between a given location and the capital city of its corresponding department.
-
D.
stateCapitalProximity
chosen
Indicates the spatial closeness or distance between a state’s capital city and another specified location.
-
E.
prefectureCapitalDistance
Indicates the distance between a prefecture and its designated capital city.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2ea9b3c8190b11518b259d5825c |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:43 a.m.