Triple
T35137728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldur's Gate: Dark Alliance II |
E1014619
|
entity |
| Predicate | hasPlayableClass |
P190403
|
FINISHED |
| Object | barbarian |
—
|
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: barbarian | Statement: [Baldur's Gate: Dark Alliance II, hasPlayableClass, barbarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayableClass Context triple: [Baldur's Gate: Dark Alliance II, hasPlayableClass, barbarian]
-
A.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
B.
playableClasses
chosen
Indicates that the referenced entity can be used or selected as a character class that a player is allowed to play.
-
C.
playableInClass
Indicates that something (such as a skill, item, or ability) can be used or is valid for use within a particular class or category.
-
D.
hasProtagonistClass
Indicates that a work’s main character belongs to a specified class or category.
-
E.
playableRaceForClass
Indicates that a particular race is allowed or eligible to be chosen as a playable option for a given character class.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:02 p.m.