Triple
T11658810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ender Dragon |
E277072
|
entity |
| Predicate | immuneTo |
P78314
|
FINISHED |
| Object | lava |
—
|
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: lava | Statement: [Ender Dragon, immuneTo, lava]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immuneTo Context triple: [Ender Dragon, immuneTo, lava]
-
A.
immunity
chosen
Indicates that an entity is protected against or not affected by a particular agent, condition, or influence.
-
B.
immuneResponseType
Indicates the specific kind or category of immune reaction that occurs in response to a particular stimulus or agent.
-
C.
allergenicity
Indicates that one entity has the capacity to cause an allergic reaction in another entity.
-
D.
preExistingImmunityInHumans
Indicates that humans already possess some level of immune protection against a particular agent, condition, or exposure prior to a specified event or intervention.
-
E.
antigen
Indicates that one entity functions as an antigen in relation to another, typically provoking or being recognized by an immune response.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.