Triple
T29655678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldaris |
E750255
|
entity |
| Predicate | appearsInCampaign |
P151240
|
FINISHED |
| Object | StarCraft: Episode I – Rebel Yell |
—
|
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: StarCraft: Episode I – Rebel Yell | Statement: [Aldaris, appearsInCampaign, StarCraft: Episode I – Rebel Yell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInCampaign Context triple: [Aldaris, appearsInCampaign, StarCraft: Episode I – Rebel Yell]
-
A.
partOfCampaign
Indicates that an entity participates in, belongs to, or is included within a specific campaign.
-
B.
associatedWithCampaigns
chosen
Indicates that an entity has a connection or linkage to one or more campaigns, such as participation, inclusion, or relevance to those campaigns.
-
C.
appearsInMission
Indicates that an entity participates in, is featured in, or occurs within a particular mission.
-
D.
testCampaign
Indicates that an entity is involved in or associated with a campaign conducted for testing, experimentation, or evaluation purposes.
-
E.
supportedCampaignOf
Indicates that one entity actively backed, promoted, or provided assistance to the campaign associated with 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 6:55 p.m.