Triple
T37462396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jungle Giants |
E930949
|
entity |
| Predicate | startOfGameEffect |
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: [Jungle Giants, startOfGameEffect, Appears in opening hand if in deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfGameEffect Context triple: [Jungle Giants, startOfGameEffect, Appears in opening hand if in deck]
-
A.
starterInGameMode
Indicates that an entity serves as the initial or primary participant when a specific game mode is active.
-
B.
startingRound
Indicates that a particular round, phase, or stage of an event or process is beginning or being initiated.
-
C.
playerStartsWith
chosen
Indicates that a player begins a game, session, or sequence already possessing or being associated with a specified item, state, or attribute.
-
D.
gameAct
Indicates that an entity performs or participates in an action or event within a game context.
-
E.
allegedStartGame
Indicates that an entity is claimed or reported, but not confirmed, to have initiated a game.
- 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_6a00d08e8fac8190b59359134e6e1c03 |
completed | May 10, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_6a00d0127c088190a6f5b360450af113 |
completed | May 10, 2026, 6:36 p.m. |
Created at: May 3, 2026, 4:17 p.m.