Triple
T30993838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lead, South Dakota |
E789738
|
entity |
| Predicate | hostedExperimentType |
P1591
|
FINISHED |
| Object | neutrino physics experiments |
—
|
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: neutrino physics experiments | Statement: [Lead, South Dakota, hostedExperimentType, neutrino physics experiments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedExperimentType Context triple: [Lead, South Dakota, hostedExperimentType, neutrino physics experiments]
-
A.
hostsExperiment
chosen
Indicates that one entity provides the environment or infrastructure in which another entity’s experiment is conducted or run.
-
B.
trialTypeHosted
Indicates that a particular trial was organized, conducted, or hosted by a specified entity.
-
C.
experimentSponsor
Indicates that an entity provides funding, resources, or support to sponsor a particular experiment.
-
D.
includesExperiment
Indicates that one entity contains or encompasses a specific experiment as part of its scope, composition, or content.
-
E.
hasTypeOfExperiment
Indicates that an experiment is associated with or classified under a specific type or category of experiment.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 8:56 p.m.