Triple
T7338042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R-pentomino |
E169178
|
entity |
| Predicate | ruleFamily |
P11488
|
FINISHED |
| Object | outer-totalistic cellular automaton |
—
|
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: outer-totalistic cellular automaton | Statement: [R-pentomino, ruleFamily, outer-totalistic cellular automaton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleFamily Context triple: [R-pentomino, ruleFamily, outer-totalistic cellular automaton]
-
A.
familyRule
Indicates a rule, norm, or guideline that governs relationships or behavior within a family context.
-
B.
macroFamily
Indicates that two or more language families are hypothesized to share a common higher-level genetic origin, forming a larger proposed macro-family grouping.
-
C.
routeFamily
Indicates a familial or hierarchical relationship between routes, such as one route being derived from, grouped with, or subordinate to another within a routing structure.
-
D.
patternFamily
chosen
Indicates that one entity belongs to, or is categorized within, a family or group of related patterns defined by the other entity.
-
E.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:04 p.m.