Triple
T16960883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa América 1957 matches |
E411422
|
entity |
| Predicate | arePlayedBy |
P125392
|
FINISHED |
| Object | national representative teams |
—
|
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: national representative teams | Statement: [Copa América 1957 matches, arePlayedBy, national representative teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arePlayedBy Context triple: [Copa América 1957 matches, arePlayedBy, national representative teams]
-
A.
oftenPlayedBy
Indicates that one entity frequently performs, portrays, or executes another entity, such as a role, character, or piece of music.
-
B.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
portrayedByAlsoPlays
Indicates that the actor who portrays a given character also plays another specified role or character.
-
D.
friendPlayedBy
Indicates that one entity portrays or acts as the friend of another entity in a performance or narrative context.
-
E.
portrayedBy
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0209a9081909d9c62456bc16e14 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.