Triple
T13119541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Leaf |
E311685
|
entity |
| Predicate | canBeStoredInInventory |
P100809
|
FINISHED |
| Object | yes (in some games) |
—
|
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: yes (in some games) | Statement: [Super Leaf, canBeStoredInInventory, yes (in some games)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeStoredInInventory Context triple: [Super Leaf, canBeStoredInInventory, yes (in some games)]
-
A.
canBeStoredFor
Indicates that something is suitable or allowed to be kept in storage for a certain duration or under certain conditions.
-
B.
hasInventorySystem
Indicates that an entity possesses or utilizes a system for tracking, managing, and controlling its inventory.
-
C.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
D.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
-
E.
canBeHeldIn
chosen
Indicates that one entity is capable of being contained, hosted, or conducted within another entity.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98196e69081909111407ee3d9f08e |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.