Triple
T37508266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forsworn rebellion |
E932151
|
entity |
| Predicate | playerInvolvement |
P16084
|
FINISHED |
| Object | players aid Kyrian against Forsworn |
—
|
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: players aid Kyrian against Forsworn | Statement: [Forsworn rebellion, playerInvolvement, players aid Kyrian against Forsworn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerInvolvement Context triple: [Forsworn rebellion, playerInvolvement, players aid Kyrian against Forsworn]
-
A.
playerInvolved
chosen
Indicates that a specific player participates in, is associated with, or takes part in a particular event, action, or situation.
-
B.
typeOfInvolvement
Indicates the specific role, capacity, or manner in which one entity is involved with or participates in another entity or activity.
-
C.
sportsInvolvement
Indicates the nature or extent of an entity’s participation in, association with, or role within a sport or sporting activity.
-
D.
leagueInvolvement
Indicates that an entity participates in, is affiliated with, or is otherwise involved in a particular league.
-
E.
playedInMatch
Indicates that an entity participated as a player in a particular match.
- 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_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 3, 2026, 4:17 p.m.