Triple
T37503769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlemode |
E932038
|
entity |
| Predicate | teamConfiguration |
P170005
|
FINISHED |
| Object | 1 Slayer vs 2 demons |
—
|
LITERAL FINISHED |
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: 1 Slayer vs 2 demons | Statement: [Battlemode, teamConfiguration, 1 Slayer vs 2 demons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamConfiguration Context triple: [Battlemode, teamConfiguration, 1 Slayer vs 2 demons]
-
A.
teamLineup
chosen
Indicates the assignment and ordering of participants or members that make up a specific team configuration for an event or activity.
-
B.
teamComponent
Indicates that one entity functions as a component, member, or sub-unit within a larger team or group entity.
-
C.
teamDistribution
Indicates how members or resources are allocated or spread across different teams.
-
D.
managerTeam1
Indicates that an entity serves as the manager or leader of a specific team (team1) within an organization.
-
E.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.