Triple
T7030618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conway’s soldiers |
E163258
|
entity |
| Predicate | movementRule |
P6160
|
FINISHED |
| Object | pieces move by orthogonal jumps over adjacent pieces |
—
|
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: pieces move by orthogonal jumps over adjacent pieces | Statement: [Conway’s soldiers, movementRule, pieces move by orthogonal jumps over adjacent pieces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementRule Context triple: [Conway’s soldiers, movementRule, pieces move by orthogonal jumps over adjacent pieces]
-
A.
movementType
chosen
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
B.
movementRole
Indicates the specific function or capacity an entity has within a movement or motion-related activity (e.g., mover, path, source, or goal).
-
C.
movementLocation
Indicates a relationship where an entity moves to, from, or through a specified location.
-
D.
movementDomain
Indicates the general area, medium, or context within which a movement or motion takes place.
-
E.
movementAcross
Indicates movement of an entity from one side or area to another, traversing through or over an intervening space or boundary.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.