Triple
T38587838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Three Hammers |
E932384
|
entity |
| Predicate | hasLeaderRepresentative |
P14217
|
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: [Council of Three Hammers, hasLeaderRepresentative, Muradin Bronzebeard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeaderRepresentative Context triple: [Council of Three Hammers, hasLeaderRepresentative, Muradin Bronzebeard]
-
A.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
B.
hasLeaderParticipant
Indicates that an entity participates in an event or activity in the role of a leader.
-
C.
hasMainRepresentative
chosen
Indicates that one entity serves as the primary or official representative of another entity.
-
D.
hasRepresentativeRank
Indicates that an entity holds or is assigned a particular rank that serves as its official or primary representative status within a given context.
-
E.
hasProminentLeaderFromState
Indicates that an entity has a leading or highly influential figure whose origin or primary affiliation is with a specified state.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:32 p.m.