Triple
T24874647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass Effect (2007 video game) |
E622533
|
entity |
| Predicate | seriesStart |
P107629
|
FINISHED |
| Object | Mass Effect (video game series) |
—
|
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: Mass Effect (video game series) | Statement: [Mass Effect (2007 video game), seriesStart, Mass Effect (video game series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesStart Context triple: [Mass Effect (2007 video game), seriesStart, Mass Effect (video game series)]
-
A.
seriesRunStart
Indicates the point in time or event at which a particular series or sequence of related items begins.
-
B.
seriesWith
Indicates that one entity is part of, or grouped together in, the same series or sequence as another entity.
-
C.
seriesRun
Indicates that one entity is a specific run, edition, or installment within an ongoing series associated with another entity.
-
D.
seriesBy
Indicates that one entity is the creator, author, or originator of a series to which the other entity belongs.
-
E.
seriesOrigin
chosen
Indicates that one entity is the original source or starting point from which a series or sequence of related entities is derived.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:23 a.m.