Triple
T35386947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-Switch |
E1022814
|
entity |
| Predicate | canBeStackedWithObjects |
P100802
|
FINISHED |
| Object | true 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: true in some games | Statement: [P-Switch, canBeStackedWithObjects, true in some games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeStackedWithObjects Context triple: [P-Switch, canBeStackedWithObjects, true in some games]
-
A.
stackableUpTo
Indicates that one item can be safely or feasibly placed on top of identical or related items up to a specified maximum number in a vertical stack.
-
B.
stackable
chosen
Indicates that one entity can be placed on top of another in a stable, orderly manner, typically allowing multiple such entities to be arranged vertically.
-
C.
canBePlacedUnder
Indicates that one entity is allowed or able to be positioned beneath another entity in a spatial or structural arrangement.
-
D.
isStackedWith
Indicates that one object is positioned directly on top of or beneath another object so that they form a vertical stack together.
-
E.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:03 p.m.