Triple
T29340088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purple Tentacle |
E744012
|
entity |
| Predicate | publisherOfMainGame |
P87866
|
FINISHED |
| Object | LucasArts |
—
|
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: LucasArts | Statement: [Purple Tentacle, publisherOfMainGame, LucasArts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfMainGame Context triple: [Purple Tentacle, publisherOfMainGame, LucasArts]
-
A.
gamePublisherOfAppearance
Indicates that one entity is the publisher responsible for releasing a particular appearance or edition of a game.
-
B.
gamePublisherOfWork
chosen
Indicates that one entity is the publisher responsible for releasing or distributing a particular game work.
-
C.
gameProducer
Indicates that one entity is the producer responsible for creating, managing, or overseeing the development of a game associated with another entity.
-
D.
publisherOfFranchise
Indicates that an entity serves as the publishing company responsible for releasing or distributing a particular franchise.
-
E.
publisherOfPrintVersion
Indicates that an entity serves as the publisher responsible for the printed (physical) version 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 28, 2026, 1:33 p.m.