Triple
T19833185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cowboys |
E476512
|
entity |
| Predicate | protagonistGroupRole |
P20969
|
FINISHED |
| Object | inexperienced cowhands |
—
|
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: inexperienced cowhands | Statement: [The Cowboys, protagonistGroupRole, inexperienced cowhands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistGroupRole Context triple: [The Cowboys, protagonistGroupRole, inexperienced cowhands]
-
A.
hasProtagonistGroup
Indicates that a narrative work features a central group of characters who collectively serve as the main protagonists.
-
B.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
C.
protagonistAllegiance
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
D.
protagonistType
chosen
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
E.
mainProtagonistTeamMember
Indicates that an entity is a member of the primary team or group associated with the main protagonist.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656cf7e488190b4be28b5e7b363bf |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.