Triple
T13926381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleopas |
E334870
|
entity |
| Predicate | distanceOfJourney |
P63487
|
FINISHED |
| Object | about seven miles from Jerusalem to Emmaus |
—
|
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: about seven miles from Jerusalem to Emmaus | Statement: [Cleopas, distanceOfJourney, about seven miles from Jerusalem to Emmaus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceOfJourney Context triple: [Cleopas, distanceOfJourney, about seven miles from Jerusalem to Emmaus]
-
A.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
B.
distanceProvidedBy
Indicates that a specific distance value is supplied or made available by a particular source or provider.
-
C.
trailDistanceContext
Indicates the contextual distance or separation between entities along a trail, path, or route.
-
D.
trailDistanceApprox
chosen
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
E.
distance
Indicates the spatial separation or length between two points, objects, or locations.
- F. None of above.
Provenance (3 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa7e9248190b0523415b9224e2f |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.