Triple
T38588550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for Lordaeron |
E932399
|
entity |
| Predicate | playerParticipation |
P15194
|
FINISHED |
| Object | Alliance players |
—
|
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: Alliance players | Statement: [Battle for Lordaeron, playerParticipation, Alliance players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerParticipation Context triple: [Battle for Lordaeron, playerParticipation, Alliance players]
-
A.
resultOfParticipation
Indicates that something occurs or is produced as a consequence of an entity’s participation in an event or activity.
-
B.
teamParticipated
chosen
Indicates that a team took part in or was involved in a particular event, activity, or competition.
-
C.
participationStatus
Indicates the current state or condition of an entity’s involvement in an event, activity, or process (e.g., planned, active, completed, or cancelled participation).
-
D.
participantStatus
Indicates the role, condition, or level of involvement that a participant has within a specific event, process, or relationship.
-
E.
leagueParticipations
Indicates participation relationships where an entity takes part in one or more leagues or league seasons.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.