Triple
T35009490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brotherhood Outcasts |
E1009905
|
entity |
| Predicate | relationshipWithPlayer |
P139057
|
FINISHED |
| Object | potential ally |
—
|
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: potential ally | Statement: [Brotherhood Outcasts, relationshipWithPlayer, potential ally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithPlayer Context triple: [Brotherhood Outcasts, relationshipWithPlayer, potential ally]
-
A.
relationshipToPlayer
chosen
Indicates the type of personal or social connection an entity has with the player.
-
B.
associatedWithPlayers
Indicates a relationship in which one or more players are connected, linked, or otherwise involved with the referenced entity.
-
C.
hasRelationToPlayerReputation
Indicates that an entity’s state, behavior, or outcomes are influenced by, or directly linked to, the player’s reputation.
-
D.
playerRelations
Indicates the nature or status of the relationship between players, such as alliances, rivalries, or other interpersonal dynamics.
-
E.
relationToLeague
Indicates the type or nature of a team's or participant's association with a specific league (e.g., membership, affiliation, or standing).
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.