Triple
T28612912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega arcade systems |
E724210
|
entity |
| Predicate | notableManufacturerDivision |
P82739
|
FINISHED |
| Object | Sega AM2 |
—
|
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 AM2 | Statement: [Sega arcade systems, notableManufacturerDivision, Sega AM2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableManufacturerDivision Context triple: [Sega arcade systems, notableManufacturerDivision, Sega AM2]
-
A.
manufacturerDivision
chosen
Indicates that one entity is a division, branch, or subdivision within the organizational structure of a manufacturing company.
-
B.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
C.
manufacturedBy
Indicates that an item or product is produced or created by a specific manufacturer or maker.
-
D.
manufacturerSubsidiaryOf
Indicates that a manufacturer operates as a subsidiary company that is owned or controlled by another entity.
-
E.
alsoManufacturedBy
Indicates that an item or product is produced by an additional manufacturer beyond the primary or previously mentioned one.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01416f8a8c8190abc12f68bd23dcc3 |
completed | May 11, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_6a013f3bc2e48190a51ec2707bbdd474 |
completed | May 11, 2026, 2:30 a.m. |
Created at: April 28, 2026, 4:30 a.m.