Triple
T1483747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game of Life |
E29416
|
entity |
| Predicate | typicalImplementation |
P12982
|
FINISHED |
| Object | computer simulation |
—
|
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: computer simulation | Statement: [Game of Life, typicalImplementation, computer simulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalImplementation Context triple: [Game of Life, typicalImplementation, computer simulation]
-
A.
typicalDeployment
Indicates that one entity represents the standard or most commonly used deployment configuration or pattern for the other entity.
-
B.
mandatesImplementationOf
Indicates that one entity requires or enforces the implementation or execution of another entity (such as a policy, standard, or procedure).
-
C.
commonlyImplementedBy
Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing entities.
-
D.
mostWidelyUsedImplementationOf
chosen
Indicates that one implementation of something is the most commonly or widely used version among all its implementations.
-
E.
fullyImplementedBy
Indicates that something (such as a specification, design, or requirement) is completely realized or carried out by a particular implementation or 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.