Triple
T37662195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Husk (Minecraft) |
E937740
|
entity |
| Predicate | hungerEffectDurationHard |
P18280
|
FINISHED |
| Object | 15 seconds |
—
|
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: 15 seconds | Statement: [Husk (Minecraft), hungerEffectDurationHard, 15 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hungerEffectDurationHard Context triple: [Husk (Minecraft), hungerEffectDurationHard, 15 seconds]
-
A.
fastingDuration
Indicates the length of time that an entity abstains from eating (and possibly drinking), typically as part of a fasting practice.
-
B.
effectDuration
chosen
Indicates the length of time for which an effect remains active or valid.
-
C.
hasDifficultyEffect
Indicates that one entity causes a change in the difficulty level or challenge associated with another entity or activity.
-
D.
hadEffectUntil
Indicates that an effect or condition held true up to a specific time or event, after which it no longer applied.
-
E.
recoveryDuration
Indicates the length of time required for an entity to return to a normal or functional state after an event, condition, or disruption.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.