Triple
T26163843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UltrAslan |
E654188
|
entity |
| Predicate | relatedToRivalries |
P101805
|
FINISHED |
| Object | Fenerbahçe–Galatasaray rivalry |
—
|
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: Fenerbahçe–Galatasaray rivalry | Statement: [UltrAslan, relatedToRivalries, Fenerbahçe–Galatasaray rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToRivalries Context triple: [UltrAslan, relatedToRivalries, Fenerbahçe–Galatasaray rivalry]
-
A.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
B.
hasRivalryIn
Indicates that two entities are in a state of competition or opposition within a specific domain, context, or field.
-
C.
associatedWithRivalryGame
Indicates that there is a connection or involvement between entities specifically in the context of a rivalry game.
-
D.
hasRivalryRoot
Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
-
E.
isPartOfRivalry
chosen
Indicates that one entity participates as a member or component in an ongoing rivalry involving another entity.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 26, 2026, 8:31 p.m.