Triple
T22272876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga Sudamericana de Clubes |
E550522
|
entity |
| Predicate | primaryRoleInHierarchy |
P147655
|
FINISHED |
| Object | secondary continental club tournament |
—
|
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: secondary continental club tournament | Statement: [Liga Sudamericana de Clubes, primaryRoleInHierarchy, secondary continental club tournament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleInHierarchy Context triple: [Liga Sudamericana de Clubes, primaryRoleInHierarchy, secondary continental club tournament]
-
A.
principalRoleIn
Indicates that an entity holds the primary or leading role in a particular context, activity, or relationship.
-
B.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
-
C.
primaryServiceRole
Indicates the main or most important functional role that a service performs in relation to other entities or processes.
-
D.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
E.
currentPrimaryRole
Indicates the role an entity is presently holding as its main or most important function or position.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea449648190bb89ca292d32f59d |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.