Triple
T29999164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars Arcade |
E762112
|
entity |
| Predicate | publisherForPort |
P141466
|
FINISHED |
| Object | Sega (32X version) |
—
|
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 (32X version) | Statement: [Star Wars Arcade, publisherForPort, Sega (32X version)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherForPort Context triple: [Star Wars Arcade, publisherForPort, Sega (32X version)]
-
A.
parentPublisher
Indicates that one publisher entity is the direct parent or owning publisher of another publisher entity.
-
B.
publishesTo
Indicates that one entity distributes, releases, or makes content available to another entity or destination.
-
C.
publisherAssociatedWith
chosen
Indicates a relationship where a publisher is connected or linked to another entity, such as by publishing, distributing, or otherwise being involved with its content or materials.
-
D.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
E.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 29, 2026, 6:40 p.m.