Triple
T16614277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super-Kamiokande Collaboration |
E403651
|
entity |
| Predicate | detectorLocatedAt |
P76038
|
FINISHED |
| Object | 1,000 meters underground |
—
|
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: 1,000 meters underground | Statement: [Super-Kamiokande Collaboration, detectorLocatedAt, 1,000 meters underground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectorLocatedAt Context triple: [Super-Kamiokande Collaboration, detectorLocatedAt, 1,000 meters underground]
-
A.
farDetectorLocation
Indicates that one entity is located at or corresponds to the position of a far (distant) detector relative to another reference point or system.
-
B.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
-
C.
locatedAtTimeOfDiscovery
Indicates the place where something was situated at the moment it was first discovered.
-
D.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
E.
crewLocation
Indicates that a crew is located at, assigned to, or present in a specific place or environment.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e360983d2c8190b1fe7f18aedfbde1 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.