Triple
T34578691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griz |
E887830
|
entity |
| Predicate | rivalryAlsoKnownAs |
P2578
|
FINISHED |
| Object | Brawl of the Wild |
—
|
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: Brawl of the Wild | Statement: [Griz, rivalryAlsoKnownAs, Brawl of the Wild]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryAlsoKnownAs Context triple: [Griz, rivalryAlsoKnownAs, Brawl of the Wild]
-
A.
rivalryName
chosen
Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
-
B.
rivalryNamedAfter
Indicates that a rivalry between entities is named after a particular person, place, event, or concept.
-
C.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
D.
rivalNickname
Indicates that one entity uses or is known by a nickname specifically in the context of rivalry with another entity.
-
E.
rivalOf
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:03 a.m.