Triple
T37303721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLOO Cannon |
E926021
|
entity |
| Predicate | playerStartsWith |
P194447
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [GLOO Cannon, playerStartsWith, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerStartsWith Context triple: [GLOO Cannon, playerStartsWith, no]
-
A.
hasStartingPlayer
Indicates that a specific player is designated as the one who begins or takes the first turn in a game or activity.
-
B.
playedForStart
Indicates the time or date when an entity (typically a person) began playing for a particular team or organization.
-
C.
hasStartingPiecesPerPlayer
Indicates the number of pieces each player begins with at the start of the game.
-
D.
initialChipOption
Indicates that an entity represents the first or default chip-style selectable option presented in a set of choices.
-
E.
EastStartersIncluded
Indicates that certain starting elements or participants located in the east are included within a specified set, group, or configuration.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: May 3, 2026, 4:16 p.m.