Triple
T35581606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tic-Tac-Toe |
E1028236
|
entity |
| Predicate | hasMaximumMoves |
P203886
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Tic-Tac-Toe, hasMaximumMoves, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumMoves Context triple: [Tic-Tac-Toe, hasMaximumMoves, 9]
-
A.
hasFinishingMove
Indicates that one entity possesses or is associated with a specific, often decisive or signature, final action or move used to conclude an encounter or event.
-
B.
hasMaximumBreaks
Indicates that there is an upper limit on the number of breaks allowed or assigned in a given context.
-
C.
numberOfMovements
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
D.
hasMaxDisplacement
Indicates the maximum distance or extent to which something can move or be displaced from its original position.
-
E.
maximumMovesFormula
Indicates the formula or rule used to determine the maximum number of moves allowed in a given context or scenario.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0238010fa481909b07a5c22aa0abde |
completed | May 11, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_6a0236cfdcb481908323b67b925c76d9 |
completed | May 11, 2026, 8:06 p.m. |
| PDg | Predicate description generation | batch_6a02380061088190b77e9d6e44817444 |
completed | May 11, 2026, 8:11 p.m. |
Created at: May 3, 2026, 4:04 p.m.