Triple
T23269614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GERDA |
E588250
|
entity |
| Predicate | hostLaboratoryType |
P149927
|
FINISHED |
| Object | underground laboratory |
—
|
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: underground laboratory | Statement: [GERDA, hostLaboratoryType, underground laboratory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostLaboratoryType Context triple: [GERDA, hostLaboratoryType, underground laboratory]
-
A.
laboratoryType
chosen
Indicates the specific category or kind of laboratory associated with an entity (e.g., clinical, research, diagnostic).
-
B.
hostType
Indicates the category or kind of host associated with or responsible for the related entity or activity.
-
C.
hostsUnitType
Indicates that one entity serves as a location or platform that accommodates or contains a specified type of unit.
-
D.
aboardLaboratory
Indicates that an entity is physically present on or within a laboratory facility, such as being on board a lab-equipped platform, vehicle, or structure.
-
E.
hostLatticeFor
Indicates that one entity serves as the structural lattice framework within which another entity is incorporated, embedded, or accommodated.
- 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.