Triple
T1483908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conway’s Game of Sprouts |
E29420
|
entity |
| Predicate | rule |
P1050
|
FINISHED |
| Object | lines must not cross existing lines |
—
|
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: lines must not cross existing lines | Statement: [Conway’s Game of Sprouts, rule, lines must not cross existing lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rule Context triple: [Conway’s Game of Sprouts, rule, lines must not cross existing lines]
-
A.
ruleOfLife
Indicates a guiding principle, norm, or code that governs how an entity should live or behave.
-
B.
restriction
chosen
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
-
C.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
D.
notableRule
Indicates that a rule or regulation is particularly significant, prominent, or noteworthy within a given context.
-
E.
protocolRule
Indicates that a specified rule or constraint governs how a protocol should be used, structured, or executed between entities.
- 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.