Triple
T27317805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skenfrith |
E689396
|
entity |
| Predicate | distanceToMonmouth |
P199226
|
FINISHED |
| Object | approximately 6 miles northwest |
—
|
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 6 miles northwest | Statement: [Skenfrith, distanceToMonmouth, approximately 6 miles northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMonmouth Context triple: [Skenfrith, distanceToMonmouth, approximately 6 miles northwest]
-
A.
distanceToPoughkeepsie
Indicates the spatial distance between a given entity and the location of Poughkeepsie.
-
B.
distanceToMonroe
Indicates the measured distance between a given entity and the location named Monroe.
-
C.
distanceToTrenton
Indicates the spatial distance between a given entity and the location identified as Trenton.
-
D.
distanceFromHobokenTerminal
Indicates the measured distance between a given location and Hoboken Terminal.
-
E.
distanceToHudsonRiver
Indicates the measured or specified distance between a given entity’s location and the Hudson River.
- F. None of above. chosen
Provenance (4 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
| PDg | Predicate description generation | batch_69ff27b0385c8190bccf340d26268f77 |
completed | May 9, 2026, 12:25 p.m. |
Created at: April 27, 2026, 11:31 a.m.