Triple
T37461577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beckoner of Evil |
E930929
|
entity |
| Predicate | supportsComboWith |
P194219
|
FINISHED |
| Object | Brann Bronzebeard |
E2226905
|
NE 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: Brann Bronzebeard | Statement: [Beckoner of Evil, supportsComboWith, Brann Bronzebeard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsComboWith Context triple: [Beckoner of Evil, supportsComboWith, Brann Bronzebeard]
-
A.
allowsCombination
chosen
Indicates that one entity permits or supports being combined or used together with another entity.
-
B.
supportsCompanion
Indicates that one entity provides assistance, encouragement, or backing to another entity in a companion or partner role.
-
C.
alsoSupports
Indicates that an entity, in addition to its primary or previously stated function, provides support for another entity, feature, or activity.
-
D.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
E.
supportsCommodity
Indicates that one entity provides the necessary functionality, infrastructure, or compatibility for another entity to handle, use, or trade a specified commodity.
- F. None of above.
Provenance (4 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a408c31a2148190bd812a2493e233ba |
completed | June 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.