Triple
T27885529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Checkers |
E705212
|
entity |
| Predicate | usesStartingRowsPerPlayer |
P177527
|
FINISHED |
| Object | three rows |
—
|
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: three rows | Statement: [Checkers, usesStartingRowsPerPlayer, three rows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStartingRowsPerPlayer Context triple: [Checkers, usesStartingRowsPerPlayer, three rows]
-
A.
originalPlayersPerTeam
Indicates the number of players that each team initially had at the start of a game or season.
-
B.
oversPerSide
Indicates the number of overs allocated to each side (team or player) in a match or contest.
-
C.
hasLeadCountPerSide
Indicates the number of lead elements or units associated with each side in a given context or configuration.
-
D.
numberOfPlayersPerTeam
Indicates the quantity of players that are assigned to or allowed on each team in a given context.
-
E.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 27, 2026, 6:32 p.m.