Triple
T6022614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waste Isolation Pilot Plant |
E134098
|
entity |
| Predicate | barrierType |
P53911
|
FINISHED |
| Object | engineered barriers |
—
|
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: engineered barriers | Statement: [Waste Isolation Pilot Plant, barrierType, engineered barriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: barrierType Context triple: [Waste Isolation Pilot Plant, barrierType, engineered barriers]
-
A.
typicalBarrierType
chosen
Indicates the usual or characteristic type of barrier associated with or used in a given context or situation.
-
B.
banType
Indicates the specific category or kind of prohibition or restriction that has been applied.
-
C.
crossingType
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
-
D.
ridgeType
Indicates the specific morphological or structural category that a ridge belongs to within a classification of ridge forms.
-
E.
blockadeType
Indicates the specific kind or category of blockade involved in the relationship or action.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04fbbf03c8190baf449a5d393af5c |
completed | March 22, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.