Triple
T5832602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crowland |
E129386
|
entity |
| Predicate | distanceToSpalding |
P67435
|
FINISHED |
| Object | approximately 10 miles south-east |
—
|
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 10 miles south-east | Statement: [Crowland, distanceToSpalding, approximately 10 miles south-east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSpalding Context triple: [Crowland, distanceToSpalding, approximately 10 miles south-east]
-
A.
distanceFromDesMoines
Indicates the physical distance between a given location and the city of Des Moines.
-
B.
distanceToSpringfield
Indicates the measured distance between a given location and the place named Springfield.
-
C.
distanceToSaintPaul
Indicates the measured spatial distance between a given entity and the location of Saint Paul.
-
D.
distanceToMadison
Indicates the spatial distance between a given entity and the location identified as Madison.
-
E.
distanceToLancaster
Indicates the measured distance between a given entity’s location and the location of Lancaster.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c044a9c4f0819081b8c196932883f6 |
completed | March 22, 2026, 7:36 p.m. |
Created at: March 22, 2026, 3:54 p.m.