Triple
T23269589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GERDA |
E588250
|
entity |
| Predicate | operatesDeepUnderground |
P92992
|
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: [GERDA, operatesDeepUnderground, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesDeepUnderground Context triple: [GERDA, operatesDeepUnderground, true]
-
A.
operatedUnderground
chosen
Indicates that an entity conducted its activities or operations beneath the surface of the ground, rather than at or above ground level.
-
B.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
C.
undergroundZone
Indicates that something is located in, associated with, or occurring within an area beneath the ground surface.
-
D.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
-
E.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957324bc8190b8b53d4b18386151 |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:45 p.m.