Triple
T10589494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naranjas de Villa Clara |
E249944
|
entity |
| Predicate | hasAchievementStatus |
P10716
|
FINISHED |
| Object | historically successful Cuban club |
—
|
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: historically successful Cuban club | Statement: [Naranjas de Villa Clara, hasAchievementStatus, historically successful Cuban club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAchievementStatus Context triple: [Naranjas de Villa Clara, hasAchievementStatus, historically successful Cuban club]
-
A.
hasAchievementType
Indicates that an achievement is classified under a specific type or category of achievement.
-
B.
achievementStatus
chosen
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
-
C.
hasTrophyStatus
Indicates that an entity possesses a particular trophy-related status or classification.
-
D.
hasFounderAchievement
Indicates that an entity has received or holds a notable achievement, recognition, or award specifically in its role as a founder.
-
E.
hasRelatedTrophy
Indicates that there exists a trophy that is associated with, linked to, or relevant to the given 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5277a39f08190848f24752cfa4b8f |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:40 p.m.