Triple
T762027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity test device |
E16090
|
entity |
| Predicate | locationRelativeTo |
P7317
|
FINISHED |
| Object | about 35 miles southeast of Socorro, New Mexico |
—
|
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, New Mexico | Statement: [Trinity test device, locationRelativeTo, about 35 miles southeast of Socorro, New Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeTo Context triple: [Trinity test device, locationRelativeTo, about 35 miles southeast of Socorro, New Mexico]
-
A.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
B.
locationOnUniform
Indicates that a specific location or marking appears on a uniform.
-
C.
hasRelativeLocation
chosen
Indicates that one entity is positioned in space in relation to another entity’s location.
-
D.
locatedOff
Indicates that one entity is situated away from, but in the vicinity of, another entity or reference point, rather than directly on or within it.
-
E.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6841f388190a6d08c3bf5c17fe4 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a5048a8081908d0542214142664a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.