Triple
T11659335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantom (Minecraft) |
E277082
|
entity |
| Predicate | affectedByWeather |
P32056
|
FINISHED |
| Object | Does not burn in rain |
—
|
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: Does not burn in rain | Statement: [Phantom (Minecraft), affectedByWeather, Does not burn in rain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedByWeather Context triple: [Phantom (Minecraft), affectedByWeather, Does not burn in rain]
-
A.
associatedWithWeather
chosen
Indicates a relationship where something is connected or related to weather conditions or phenomena.
-
B.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
C.
weatherConsideration
Indicates that certain conditions, decisions, or actions take into account or are influenced by the current or expected weather.
-
D.
hasWeather
Indicates that a location or environment is experiencing or characterized by a particular type of weather condition.
-
E.
hasSevereWeatherRisk
Indicates that an entity is exposed to or associated with a high likelihood of severe or hazardous weather conditions.
- 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_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.