Triple
T37204423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNT.WAD |
E922127
|
entity |
| Predicate | gameCampaign |
P82481
|
FINISHED |
| Object | TNT: Evilution |
—
|
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: TNT: Evilution | Statement: [TNT.WAD, gameCampaign, TNT: Evilution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameCampaign Context triple: [TNT.WAD, gameCampaign, TNT: Evilution]
-
A.
plannedCampaign
Indicates that an entity has designed and scheduled a campaign to be executed in the future.
-
B.
conquestCampaign
Indicates a military or strategic campaign undertaken with the goal of conquering and taking control of a target entity or territory.
-
C.
testCampaign
Indicates that an entity is involved in or associated with a campaign conducted for testing, experimentation, or evaluation purposes.
-
D.
campaign
Indicates that an entity actively organizes or conducts a coordinated effort or series of actions aimed at achieving a specific goal, often in political, commercial, or social contexts.
-
E.
campaignDescriptor
chosen
Indicates that one entity serves as a descriptive label or characterization for a particular 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.