Triple
T37539492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronzebeard clan |
E933288
|
entity |
| Predicate | leaderOnCouncilOfThreeHammers |
P189767
|
FINISHED |
| Object | Muradin Bronzebeard |
—
|
NE NERFINISHED |
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: Muradin Bronzebeard | Statement: [Bronzebeard clan, leaderOnCouncilOfThreeHammers, Muradin Bronzebeard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderOnCouncilOfThreeHammers Context triple: [Bronzebeard clan, leaderOnCouncilOfThreeHammers, Muradin Bronzebeard]
-
A.
mainLeader3
Indicates that an entity serves as the third primary or most prominent leader within a specified group, organization, or context.
-
B.
holyLeagueLeader
Indicates that the subject serves as the leader of a Holy League, an alliance formed for religiously motivated political or military purposes.
-
C.
heldCouncil
Indicates that an entity organized and conducted a formal meeting or assembly for discussion or decision-making with other participants.
-
D.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
E.
thirdLegendary
Indicates that an entity is the third member in a sequence or set of legendary entities.
- F. None of above. chosen
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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: May 3, 2026, 4:17 p.m.