Triple
T37459240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fel Reaver |
E930875
|
entity |
| Predicate | hasTribeSynergy |
P187886
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fel Reaver, hasTribeSynergy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribeSynergy Context triple: [Fel Reaver, hasTribeSynergy, true]
-
A.
classTribeSynergy
Indicates a synergistic relationship where a character’s class and tribe traits interact to provide combined or enhanced effects.
-
B.
tribeSynergy
chosen
Indicates a cooperative or mutually enhancing relationship among members of the same tribe or group, where their combined presence or actions produce greater overall effectiveness than they would individually.
-
C.
hasMergedTribe
Indicates that one tribe has combined or unified with another tribe to form a single merged group.
-
D.
hasTribalPresence
Indicates that a tribal group is present, active, or represented in relation to the referenced entity or location.
-
E.
usedByTribe
Indicates that something is utilized or employed by a particular tribe.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: May 3, 2026, 4:17 p.m.