Triple
T21787942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudbury Neutrino Observatory |
E537889
|
entity |
| Predicate | depthInRock |
P145645
|
FINISHED |
| Object | about 6,000 meters water equivalent |
—
|
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: about 6,000 meters water equivalent | Statement: [Sudbury Neutrino Observatory, depthInRock, about 6,000 meters water equivalent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthInRock Context triple: [Sudbury Neutrino Observatory, depthInRock, about 6,000 meters water equivalent]
-
A.
depthBelowSurfaceInMeters
Indicates the vertical distance, measured in meters, that something is located below a reference surface level.
-
B.
gorgeDepth
Indicates the measured vertical distance from a gorge’s rim down to its lowest point.
-
C.
buriedDepth
Indicates the depth at which one entity is buried beneath a reference surface or another entity.
-
D.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
E.
hasCaveEntranceDepth
Indicates the depth or vertical distance of a cave’s entrance relative to a reference level (such as ground surface or sea level).
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621c68588190977891055e80a499 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6c3a2898881909748935cf92f898c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 6:52 p.m.