Triple
T15535431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DK Mountain |
E370326
|
entity |
| Predicate | hasRespawnMechanic |
P99633
|
FINISHED |
| Object | Lakitu recovery when falling |
—
|
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: Lakitu recovery when falling | Statement: [DK Mountain, hasRespawnMechanic, Lakitu recovery when falling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRespawnMechanic Context triple: [DK Mountain, hasRespawnMechanic, Lakitu recovery when falling]
-
A.
hasRespawn
chosen
Indicates that an entity is able to reappear or be recreated after being removed, destroyed, or having previously ceased to exist.
-
B.
hasBedRespawn
Indicates that an entity has a bed set as its current respawn location.
-
C.
hasAnchorRespawn
Indicates that an entity is responsible for triggering or managing the respawn of an associated anchor.
-
D.
killMechanism
Indicates the method or process by which one entity causes the death or destruction of another.
-
E.
isFrequentlyRevived
Indicates that an entity is brought back, restored, or reintroduced many times over a period.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.