Triple
T35329459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIA Desgenettes |
E1020277
|
entity |
| Predicate | hasLaboratoryService |
P95935
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [HIA Desgenettes, hasLaboratoryService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaboratoryService Context triple: [HIA Desgenettes, hasLaboratoryService, yes]
-
A.
hasLaboratoryServices
chosen
Indicates that one entity provides or makes available laboratory services to another entity or within a given context.
-
B.
hasKeyLaboratory
Indicates that an entity possesses or is associated with a designated key laboratory, typically as an important research or development facility under its responsibility.
-
C.
hasLaboratorySystem
Indicates that one entity possesses, uses, or is associated with a particular laboratory system.
-
D.
hasLaboratoryDiscipline
Indicates that an entity is associated with, practices, or specializes in a particular laboratory-based scientific discipline.
-
E.
hasLaboratorySpace
Indicates that an entity provides or contains designated laboratory facilities or areas for scientific or technical work.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:03 p.m.