Triple
T1483905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conway’s Game of Sprouts |
E29420
|
entity |
| Predicate | startingPosition |
P389
|
FINISHED |
| Object | finite set of dots on a sheet of paper |
—
|
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: finite set of dots on a sheet of paper | Statement: [Conway’s Game of Sprouts, startingPosition, finite set of dots on a sheet of paper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingPosition Context triple: [Conway’s Game of Sprouts, startingPosition, finite set of dots on a sheet of paper]
-
A.
startPoint
chosen
Indicates the initial location or position from which an object, path, or action begins.
-
B.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
C.
startingPark
Indicates that an entity begins or initiates its activity, route, or presence from a specified park.
-
D.
positionCoached
Indicates that one entity served as a coach for another entity in a specific position or role.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c679714c8190ac53630fb49e19c5 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.