Triple
T25601009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternal Derby of Bulgaria |
E641786
|
entity |
| Predicate | hasRivalryAxis |
P8277
|
FINISHED |
| Object | social identity |
—
|
LITERAL FINISHED |
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: social identity | Statement: [Eternal Derby of Bulgaria, hasRivalryAxis, social identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalryAxis Context triple: [Eternal Derby of Bulgaria, hasRivalryAxis, social identity]
-
A.
hasRivalryAspect
chosen
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
B.
hasRivalryRoot
Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
-
C.
hasRivalryCategory
Indicates that there exists a competitive or adversarial relationship between entities that falls into a specific classified type or category of rivalry.
-
D.
isPartOfRivalry
Indicates that one entity participates as a member or component in an ongoing rivalry involving another entity.
-
E.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 4:31 p.m.