Triple
T24238725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga I |
E603161
|
entity |
| Predicate | mostSuccessfulClubFormerName |
P155302
|
FINISHED |
| Object | Steaua București |
—
|
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: Steaua București | Statement: [Liga I, mostSuccessfulClubFormerName, Steaua București]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostSuccessfulClubFormerName Context triple: [Liga I, mostSuccessfulClubFormerName, Steaua București]
-
A.
nicknameOfClubFormerName
Indicates that a given nickname was used for a club when it had a former or previous official name.
-
B.
mostSuccessfulClub
Indicates that one club holds the highest level of success (e.g., by titles, achievements, or performance) compared to all other clubs in the given context.
-
C.
clubFormerName
Indicates that a sports club previously operated under a different official name.
-
D.
notableSuccessorClub
Indicates that one club is widely recognized as the prominent successor or continuation of another club.
-
E.
successorClubPlaysIn
Indicates that the club which succeeds another club participates in a specified league or competition.
- F. None of above. chosen
Provenance (4 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28a9d70288190ac3cd0c78e08aa90 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:03 a.m.