Triple
T35386251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invincibility Leaf |
E1022799
|
entity |
| Predicate | inGameBehavior |
P183784
|
FINISHED |
| Object | automatically equips when collected |
—
|
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: automatically equips when collected | Statement: [Invincibility Leaf, inGameBehavior, automatically equips when collected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGameBehavior Context triple: [Invincibility Leaf, inGameBehavior, automatically equips when collected]
-
A.
inGameZone
Indicates that an entity is located within a defined game zone or area of the game world.
-
B.
inGameType
Indicates that an entity participates in or belongs to a specific type or category within a game (e.g., game mode, classification, or role).
-
C.
performedInGame
Indicates that an action or event was carried out during a particular game or match.
-
D.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
E.
inGameName
Indicates that one entity is the name used by another entity within a specific game context.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: May 3, 2026, 4:03 p.m.