Triple
T37462331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open the Waygate |
E930947
|
entity |
| Predicate | positionInGameStart |
P194447
|
FINISHED |
| Object | Appears in opening hand if in deck |
—
|
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: Appears in opening hand if in deck | Statement: [Open the Waygate, positionInGameStart, Appears in opening hand if in deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInGameStart Context triple: [Open the Waygate, positionInGameStart, Appears in opening hand if in deck]
-
A.
initialPosition
Indicates the original or starting location of an entity before any movement or change in position occurs.
-
B.
playerStartsWith
chosen
Indicates that a player begins a game, session, or sequence already possessing or being associated with a specified item, state, or attribute.
-
C.
positionInAct
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
-
D.
initiatingPosition
Indicates the starting location or initial spatial position from which an action, process, or movement begins.
-
E.
positionStartTime
Indicates the time at which a position, role, or placement begins.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: May 3, 2026, 4:17 p.m.