Triple
T24466241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaidan Alenko |
E616976
|
entity |
| Predicate | promotionIn |
P156210
|
FINISHED |
| Object | Mass Effect 3 |
—
|
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 3 | Statement: [Kaidan Alenko, promotionIn, Mass Effect 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionIn Context triple: [Kaidan Alenko, promotionIn, Mass Effect 3]
-
A.
promotionFor
Indicates that one entity serves as a promotional activity, material, or campaign intended to advertise, support, or increase the visibility of another entity.
-
B.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
C.
promotionBy
Indicates that one entity advances, elevates, or publicizes another entity, typically by increasing its status, visibility, or level.
-
D.
promotionTo
Indicates that one entity is elevated or advanced to a higher rank, position, or status relative to another entity or context.
-
E.
promotionType
Indicates the specific kind or category of promotion associated with an entity or event.
- F. None of above. chosen
Provenance (4 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2993ecd988190991598832b29a131 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.