Triple
T8355613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murrisk, County Mayo |
E196673
|
entity |
| Predicate | distanceFromWestport |
P82260
|
FINISHED |
| Object | approximately 8 km |
—
|
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 km | Statement: [Murrisk, County Mayo, distanceFromWestport, approximately 8 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromWestport Context triple: [Murrisk, County Mayo, distanceFromWestport, approximately 8 km]
-
A.
distanceFromBoston
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
B.
distanceToNewport
Indicates the measured or calculated distance between a given entity and the location named Newport.
-
C.
distanceToFalmouth
Indicates the physical distance between a given location or entity and the place named Falmouth.
-
D.
distanceToHartford
Indicates the spatial distance between a given entity’s location and the city of Hartford.
-
E.
distanceToTaunton
Indicates the spatial distance between a given entity and the location Taunton.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804a344c819089c0a13fe66e3088 |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:59 p.m.