Triple
T35981195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvertails |
E1040566
|
entity |
| Predicate | hasRivalNickname |
P164548
|
FINISHED |
| Object | Fibros |
—
|
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: Fibros | Statement: [Silvertails, hasRivalNickname, Fibros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalNickname Context triple: [Silvertails, hasRivalNickname, Fibros]
-
A.
rivalNickname
chosen
Indicates that one entity uses or is known by a nickname specifically in the context of rivalry with another entity.
-
B.
contrastsWithRivalNickname
Indicates that one nickname is intentionally different from and set in opposition to a rival nickname.
-
C.
hasNicknames
Indicates that an entity is known or referred to by one or more alternative informal names.
-
D.
rivalryName
Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
-
E.
opponentNickname
Indicates that one entity is the nickname used to refer to another entity in a competitive or adversarial context.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:07 p.m.