Triple
T134111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity test site, New Mexico |
E2713
|
entity |
| Predicate | distanceFromSocorro |
P5012
|
FINISHED |
| Object | about 35 miles southeast of Socorro |
—
|
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 35 miles southeast of Socorro | Statement: [Trinity test site, New Mexico, distanceFromSocorro, about 35 miles southeast of Socorro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSocorro Context triple: [Trinity test site, New Mexico, distanceFromSocorro, about 35 miles southeast of Socorro]
-
A.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
-
B.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
C.
distanceFromBoston
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
D.
distanceFromSouthPole
Indicates the measured distance of an entity from the geographic South Pole.
-
E.
distanceToPhiladelphia
Indicates the spatial distance between a given entity’s location and the city of Philadelphia.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25788b2688190a45b39447f702551 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a25650251c81908a6ea6368cd61198 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256ea776081908fec36c3fdfb8d84 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.