Triple
T22695182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INGRID |
E561155
|
entity |
| Predicate | distanceFromNeutrinoProductionTarget |
P149333
|
FINISHED |
| Object | approximately 280 m |
—
|
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 280 m | Statement: [INGRID, distanceFromNeutrinoProductionTarget, approximately 280 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromNeutrinoProductionTarget Context triple: [INGRID, distanceFromNeutrinoProductionTarget, approximately 280 m]
-
A.
distanceFromCERN
Indicates the spatial distance between a given entity and CERN as a reference point.
-
B.
distanceToFarDetector
Indicates the measured or calculated distance from a given entity to the designated far detector.
-
C.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
D.
distanceFromMina
Indicates the spatial distance measured between Mina and another specified entity or location.
-
E.
distanceFromBol
Indicates the measured distance between an entity and a specified beginning-of-line (BOL) reference point.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789d46c881908176bc8e26f366f6 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:14 p.m.