Triple
T27885521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Checkers |
E705212
|
entity |
| Predicate | hasSecondaryGoal |
P3579
|
FINISHED |
| Object | block opponent moves |
—
|
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: block opponent moves | Statement: [Checkers, hasSecondaryGoal, block opponent moves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryGoal Context triple: [Checkers, hasSecondaryGoal, block opponent moves]
-
A.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
B.
secondaryGoal
chosen
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
-
C.
hasNonFunctionalGoal
Indicates that an entity is associated with a goal describing quality or performance constraints rather than specific functional behavior.
-
D.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
E.
hasFictionalGoal
Indicates that an entity is associated with a goal or objective that exists only within a fictional, imagined, or narrative context.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 27, 2026, 6:32 p.m.