Triple
T15309463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U7 |
E365989
|
entity |
| Predicate | isEntirelyUnderground |
P78577
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [U7, isEntirelyUnderground, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEntirelyUnderground Context triple: [U7, isEntirelyUnderground, true]
-
A.
isUndergroundOnly
chosen
Indicates that something exists, operates, or is accessible exclusively below ground level and not above ground.
-
B.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
-
C.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
D.
operatedUnderground
Indicates that an entity conducted its activities or operations beneath the surface of the ground, rather than at or above ground level.
-
E.
hasUndergroundSection
Indicates that an entity includes a portion or segment 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd176708190b0f6ba17aed92f8e |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.