Triple
T22842203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNGS underground halls |
E566111
|
entity |
| Predicate | shieldingMedium |
P117936
|
FINISHED |
| Object | rock overburden |
—
|
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: rock overburden | Statement: [LNGS underground halls, shieldingMedium, rock overburden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shieldingMedium Context triple: [LNGS underground halls, shieldingMedium, rock overburden]
-
A.
shieldMaterial
chosen
Indicates the material from which a shield is made or constructed.
-
B.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
C.
requiresShielding
Indicates that one entity must be protected or insulated from another entity or from certain conditions, typically for safety or proper functioning.
-
D.
shieldPartition
Indicates a relationship where one entity serves as a protective barrier that divides or separates another entity or space into distinct parts.
-
E.
shieldDescribedAs
Indicates that a shield is characterized or portrayed using a particular description or set of attributes.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e855abc8190b9cf8cc515090a7f |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.