Triple
T28266166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian football league system |
E712708
|
entity |
| Predicate | historicalRebranding |
P62676
|
FINISHED |
| Object | Divizia A renamed Liga I in 2006 |
—
|
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: Divizia A renamed Liga I in 2006 | Statement: [Romanian football league system, historicalRebranding, Divizia A renamed Liga I in 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRebranding Context triple: [Romanian football league system, historicalRebranding, Divizia A renamed Liga I in 2006]
-
A.
brandEvolution
Indicates how a brand’s identity, positioning, or attributes change and develop over time.
-
B.
brandHistory
Indicates the historical background, evolution, and significant past events associated with a particular brand.
-
C.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
D.
hasFormerLogo
Indicates that an entity is associated with a logo it used in the past but no longer uses.
-
E.
announcedRebrandingAs
chosen
Indicates that one entity has publicly declared it will change its name, brand, or identity to that of 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: April 27, 2026, 11:14 p.m.