Triple
T22842204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNGS underground halls |
E566111
|
entity |
| Predicate | overburdenType |
P149929
|
FINISHED |
| Object | limestone rock |
—
|
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: limestone rock | Statement: [LNGS underground halls, overburdenType, limestone rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overburdenType Context triple: [LNGS underground halls, overburdenType, limestone rock]
-
A.
overburden
Indicates that one entity places an excessive load, demand, or responsibility on another, beyond what it can reasonably handle.
-
B.
oreType
Indicates the specific kind or classification of ore associated with an entity.
-
C.
overlies
Indicates that one entity is positioned directly above and covering or resting on another entity, often with partial or complete contact.
-
D.
overarchedBy
Indicates that one entity is physically or conceptually spanned, covered, or dominated from above by another entity.
-
E.
buriedUnder
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
- 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_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. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:35 p.m.