Triple
T1901766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deal |
E37703
|
entity |
| Predicate | distanceFromDover |
P33782
|
FINISHED |
| Object | approximately 8 miles |
—
|
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 miles | Statement: [Deal, distanceFromDover, approximately 8 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDover Context triple: [Deal, distanceFromDover, approximately 8 miles]
-
A.
distanceFromBoston
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
B.
distanceToHanover
Indicates the spatial distance between a given entity and the location Hanover.
-
C.
distanceToBrighton
Indicates the measured or specified distance between a given entity or location and Brighton.
-
D.
distanceToPhiladelphia
Indicates the spatial distance between a given entity’s location and the city of Philadelphia.
-
E.
distanceToPoughkeepsie
Indicates the spatial distance between a given entity and the location of Poughkeepsie.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb34c4a64819096e12b152b84c334 |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:35 p.m.