Triple
T37665734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cappy |
E937815
|
entity |
| Predicate | coOpRole |
P21905
|
FINISHED |
| Object | second player controls Cappy |
—
|
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: second player controls Cappy | Statement: [Cappy, coOpRole, second player controls Cappy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coOpRole Context triple: [Cappy, coOpRole, second player controls Cappy]
-
A.
coOperator
chosen
Indicates that two or more entities work together as partners or collaborators in performing an activity or achieving a shared objective.
-
B.
roleInCoco
Indicates that an entity serves a specific role or function within the context of the COCO dataset or framework.
-
C.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
D.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
E.
agencyRole
Indicates that one entity serves in a specific functional or organizational capacity on behalf of, or within, another entity (such as an agency, institution, or governing body).
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e16fb881908bb74df86ab04427 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.