Triple
T23269606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GERDA |
E588250
|
entity |
| Predicate | detectorEnvironment |
P853
|
FINISHED |
| Object | liquid argon cryostat |
—
|
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: liquid argon cryostat | Statement: [GERDA, detectorEnvironment, liquid argon cryostat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectorEnvironment Context triple: [GERDA, detectorEnvironment, liquid argon cryostat]
-
A.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
B.
environmentType
chosen
Indicates the kind or category of environment associated with an entity or situation.
-
C.
detectorConfiguration
Indicates a relationship where a detector is associated with, or operates under, a specific configuration or set of parameter settings.
-
D.
displayEnvironment
Indicates that an entity presents or renders a particular environment or environmental setting for viewing or interaction.
-
E.
detectorConcept
Indicates that one entity functions as a detector whose conceptual design, type, or detection principle is characterized or specified by the other entity.
- 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.