Triple
T26253565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golly |
E656659
|
entity |
| Predicate | supportsRuleFormat |
P104471
|
FINISHED |
| Object | Life-like cellular automata rules |
—
|
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: Life-like cellular automata rules | Statement: [Golly, supportsRuleFormat, Life-like cellular automata rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRuleFormat Context triple: [Golly, supportsRuleFormat, Life-like cellular automata rules]
-
A.
supportsRuleType
chosen
Indicates that one entity is capable of handling, applying, or being compatible with a specified type of rule.
-
B.
supportsTextFormat
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified text format.
-
C.
hasFormOfRule
Indicates that one entity embodies, expresses, or takes the specific form of a rule defined by another entity.
-
D.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
E.
meetsFormat
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 26, 2026, 9:07 p.m.