Triple
T7010225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conway, Arkansas |
E162560
|
entity |
| Predicate | distanceToLittleRock |
P73646
|
FINISHED |
| Object | approximately 30 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 30 miles | Statement: [Conway, Arkansas, distanceToLittleRock, approximately 30 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLittleRock Context triple: [Conway, Arkansas, distanceToLittleRock, approximately 30 miles]
-
A.
distanceToStLouis
Indicates the measured distance between a given entity’s location and the city of St. Louis.
-
B.
distanceToMemphisApproxMiles
Indicates an approximate distance, measured in miles, between a given entity’s location and the city of Memphis.
-
C.
distanceToLouisvilleApprox
Indicates an approximate distance between a given location and Louisville.
-
D.
distanceToColumbiaMissouri
Indicates the measured or calculated distance between a given entity’s location and Columbia, Missouri.
-
E.
distanceToMontgomery
Indicates the spatial distance between a given entity and the location identified as Montgomery.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc3917c481909a288c3e56630c48 |
completed | March 27, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c790288190b7cbbaa4a5f9c91d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8a4930081908f1ae1e6ca8a514c |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:34 p.m.