Triple
T35394555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mama |
E1023035
|
entity |
| Predicate | originalPlatformRelease |
P17946
|
FINISHED |
| Object | Family Computer |
E491809
|
NE 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: Family Computer | Statement: [Mama, originalPlatformRelease, Family Computer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPlatformRelease Context triple: [Mama, originalPlatformRelease, Family Computer]
-
A.
originalPlatformGeneration
Indicates that one platform is the initial or first-generation version from which another platform or subsequent generations are derived.
-
B.
firstReleasePlatform
chosen
Indicates the platform on which something (such as a product, work, or media) was first released.
-
C.
originPlatform
Indicates the platform, system, or environment from which an entity, event, or piece of data originally comes.
-
D.
intendedReleasePlatform
Indicates the platform or medium for which something (such as a product, work, or content) is planned or designated to be released.
-
E.
earlyPlatformFor
Indicates that one entity served as an initial or precursor platform, environment, or venue enabling the development, exposure, or operation of another entity.
- F. None of above.
Provenance (4 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a382cc75b1081909041b297003248e9 |
completed | June 21, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.