Triple
T9420511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Money, Mississippi |
E227137
|
entity |
| Predicate | distanceTo Clarksdale, Mississippi |
P88762
|
FINISHED |
| Object | approximately 49 miles southeast |
—
|
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 49 miles southeast | Statement: [Money, Mississippi, distanceTo Clarksdale, Mississippi, approximately 49 miles southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceTo Clarksdale, Mississippi Context triple: [Money, Mississippi, distanceTo Clarksdale, Mississippi, approximately 49 miles southeast]
-
A.
distanceToClanton
Indicates the spatial distance between a given entity and the location identified as Clanton.
-
B.
distanceToLittleRock
Indicates the spatial distance between a given entity and the location of Little Rock.
-
C.
distanceToMontgomery
Indicates the spatial distance between a given entity and the location identified as Montgomery.
-
D.
distanceToJackson
Indicates the spatial distance or separation between a given entity and Jackson.
-
E.
distanceToMemphisApproxMiles
Indicates an approximate distance, measured in miles, between a given entity’s location and the city of Memphis.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c2528c8819087b0a21e703254b7 |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:48 p.m.