Triple
T3631566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOvA experiment |
E76966
|
entity |
| Predicate | farDetectorRegion |
P9687
|
FINISHED |
| Object | northern Minnesota |
—
|
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: northern Minnesota | Statement: [NOvA experiment, farDetectorRegion, northern Minnesota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farDetectorRegion Context triple: [NOvA experiment, farDetectorRegion, northern Minnesota]
-
A.
formationRegion
Indicates the place or area where something originates, is created, or comes into being.
-
B.
observedInRegion
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
-
C.
borderRegionPresence
Indicates the presence or occurrence of something within or along a border region between areas or territories.
-
D.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
E.
sensitivityRegion
Indicates the specific area or domain within which a subject is particularly responsive, vulnerable, or reactive to a given influence or condition.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30136e88190922bb542971b5239 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.