Triple
T20163780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oblivion |
E491777
|
entity |
| Predicate | undergroundElement |
P98017
|
FINISHED |
| Object | tunnel beneath ground level |
—
|
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: tunnel beneath ground level | Statement: [Oblivion, undergroundElement, tunnel beneath ground level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergroundElement Context triple: [Oblivion, undergroundElement, tunnel beneath ground level]
-
A.
undergroundZone
Indicates that something is located in, associated with, or occurring within an area beneath the ground surface.
-
B.
undergroundBranch
Indicates that one entity is a branch or extension of another that operates or exists in a hidden, secret, or non-public manner.
-
C.
integratedIntoUnderground
Indicates that something has been incorporated or absorbed into an underground system, structure, or environment.
-
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.
hasUndergroundLevel
chosen
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66841b7d88190af3606f762d87b24 |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.