Triple
T3631581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOvA experiment |
E76966
|
entity |
| Predicate | farDetectorCompletion |
P49680
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [NOvA experiment, farDetectorCompletion, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farDetectorCompletion Context triple: [NOvA experiment, farDetectorCompletion, 2014]
-
A.
completedWithDiscoveryOf
Indicates that an action, process, or event was brought to completion as a direct result of a particular discovery.
-
B.
requiresDetectionOf
Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
-
C.
frontLineReached
Indicates that an entity has arrived at or crossed into the designated front line or primary boundary of engagement.
-
D.
laterCompletionVersion
Indicates that one entity is a version of a completion that occurs or is produced later in time than another related version.
-
E.
usedInDetector
Indicates that something (e.g., a component, material, or method) is employed as part of a detector or detection system.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30251d881908284edeb7fe69ad8 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:23 p.m.