Triple
T17815928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Club Cerro Porteño |
E444839
|
entity |
| Predicate | mottoRole |
P53891
|
FINISHED |
| Object | symbol of popular football in Paraguay |
—
|
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: symbol of popular football in Paraguay | Statement: [Club Cerro Porteño, mottoRole, symbol of popular football in Paraguay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoRole Context triple: [Club Cerro Porteño, mottoRole, symbol of popular football in Paraguay]
-
A.
mottoOrRole
chosen
Indicates that one entity serves as the motto, slogan, or role designation associated with another entity.
-
B.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
C.
motto
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
-
D.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
E.
mottoPractice
Indicates that an entity engages in or follows a particular motto as a guiding practice or principle.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887f7d048190b6d813b9f0fab3e7 |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.