Triple
T7700298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yucca Mountain |
E174473
|
entity |
| Predicate | repositoryDepth |
P36777
|
FINISHED |
| Object | hundreds of meters below the surface |
—
|
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: hundreds of meters below the surface | Statement: [Yucca Mountain, repositoryDepth, hundreds of meters below the surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repositoryDepth Context triple: [Yucca Mountain, repositoryDepth, hundreds of meters below the surface]
-
A.
testDepth
Indicates that an entity is evaluated or measured based on how deep or thorough it is, often in terms of levels, layers, or extent below a surface or baseline.
-
B.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
-
C.
reachedDepth
Indicates that an entity has arrived at or attained a specified depth level in some medium or context.
-
D.
branchCount
Indicates the number of branches associated with a given entity or structure.
-
E.
hasDepth
chosen
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.