Triple
T24432046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass Effect fandom |
E616022
|
entity |
| Predicate | basedOnWorkPublishedBy |
P100405
|
FINISHED |
| Object | Electronic Arts |
—
|
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: Electronic Arts | Statement: [Mass Effect fandom, basedOnWorkPublishedBy, Electronic Arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnWorkPublishedBy Context triple: [Mass Effect fandom, basedOnWorkPublishedBy, Electronic Arts]
-
A.
basedOnWorkAppearedIn
Indicates that something is derived from, adapted from, or otherwise created using a work that appeared in a specified source or publication.
-
B.
basedOnWorkAuthorAssociatedWith
Indicates that one entity is derived from or related to a work whose author is associated with another specified entity.
-
C.
basedOnWorkPublisher
chosen
Indicates that one entity serves as the publisher of the work on which another entity is based.
-
D.
basedOnAuthor
Indicates that one entity is derived from, inspired by, or otherwise created on the basis of the work or contributions of a particular author.
-
E.
basedOnOwnWork
Indicates that something is derived from, created using, or directly built upon the subject’s own prior work.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29783b3208190997c47be1aa229af |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.