Triple
T37591789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zul'Gurub |
E935276
|
entity |
| Predicate | providesReputationWith |
P198351
|
FINISHED |
| Object | Zandalar Tribe |
—
|
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: Zandalar Tribe | Statement: [Zul'Gurub, providesReputationWith, Zandalar Tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesReputationWith Context triple: [Zul'Gurub, providesReputationWith, Zandalar Tribe]
-
A.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
B.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
C.
denotesReputationOf
Indicates that one entity represents, expresses, or serves as an indicator of the reputation or perceived standing of another entity.
-
D.
reputationHub
Indicates a central entity that aggregates, manages, or influences the reputations of multiple other entities.
-
E.
reputationUsedFor
Indicates that an entity’s reputation is leveraged or applied for a particular purpose, function, or outcome.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
| PDg | Predicate description generation | batch_69fedec5e1708190a0b13be7533d55d8 |
completed | May 9, 2026, 7:14 a.m. |
Created at: May 3, 2026, 4:18 p.m.