Triple
T23269582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GERDA |
E588250
|
entity |
| Predicate | usesDetectorMaterial |
P25632
|
FINISHED |
| Object | germanium-76 |
—
|
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: germanium-76 | Statement: [GERDA, usesDetectorMaterial, germanium-76]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDetectorMaterial Context triple: [GERDA, usesDetectorMaterial, germanium-76]
-
A.
usesMaterialBy
Indicates that one entity makes use of or employs a material that is provided, specified, or created by another entity.
-
B.
usesTrackMaterial
Indicates that one entity employs or incorporates a specified track material in its construction, configuration, or operation.
-
C.
isMaterialSpecific
Indicates that a relationship, rule, or property applies only to a particular material or set of materials, rather than being generally applicable.
-
D.
usesSupportMaterial
Indicates that an entity relies on or incorporates additional supporting materials or resources to carry out an action or fulfill a function.
-
E.
usedInDetector
chosen
Indicates that something (e.g., a component, material, or method) is employed as part of a detector or detection system.
- 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.