Triple
T30358694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Mark III |
E772212
|
entity |
| Predicate | companyPlatformLine |
P180638
|
FINISHED |
| Object | Sega 8-bit family |
—
|
NE NERFINISHED |
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: Sega 8-bit family | Statement: [Sega Mark III, companyPlatformLine, Sega 8-bit family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyPlatformLine Context triple: [Sega Mark III, companyPlatformLine, Sega 8-bit family]
-
A.
companyPlatform
chosen
Indicates that a company operates, provides, or is associated with a particular platform (such as a software, service, or technological environment).
-
B.
platformLine
Indicates that a platform is associated with, serves, or is aligned along a particular line (such as a transit, rail, or service line).
-
C.
corporatePlatform
Indicates a relationship where an entity serves as a corporate platform used by or provided to another entity for business-related activities or services.
-
D.
line7PlatformsType
Indicates the type or classification of platforms associated with line 7.
-
E.
platform1Services
Indicates that one entity provides or is associated with the first platform’s services for or in relation to another 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 29, 2026, 7:57 p.m.