Triple
T34487393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lazarus Effect |
E885365
|
entity |
| Predicate | hasLaboratorySerum |
P199510
|
FINISHED |
| Object | Lazarus serum |
—
|
NE NERFINISHED |
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: Lazarus serum | Statement: [The Lazarus Effect, hasLaboratorySerum, Lazarus serum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaboratorySerum Context triple: [The Lazarus Effect, hasLaboratorySerum, Lazarus serum]
-
A.
hasLaboratoryServices
Indicates that one entity provides or makes available laboratory services to another entity or within a given context.
-
B.
laboratoryAnalysis
Indicates that a sample or material is being examined, tested, or measured using scientific procedures in a laboratory setting.
-
C.
hasLaboratorySystem
Indicates that one entity possesses, uses, or is associated with a particular laboratory system.
-
D.
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.
-
E.
laboratoryFinding
Indicates that a specific result, observation, or measurement was obtained from a laboratory test or analysis.
- F. None of above. chosen
Provenance (4 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
| PDg | Predicate description generation | batch_69ff3fb151008190bf8a90f9f1c5f0c8 |
completed | May 9, 2026, 2:07 p.m. |
Created at: May 1, 2026, 2:01 a.m.