Triple
T3316678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayans M.C. |
E69697
|
entity |
| Predicate | hasProtagonistAffiliation |
P34302
|
FINISHED |
| Object | Mayans M.C. Santo Padre charter |
—
|
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: Mayans M.C. Santo Padre charter | Statement: [Mayans M.C., hasProtagonistAffiliation, Mayans M.C. Santo Padre charter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistAffiliation Context triple: [Mayans M.C., hasProtagonistAffiliation, Mayans M.C. Santo Padre charter]
-
A.
mainCharacterAffiliation
chosen
Indicates the group, organization, or side with which the main character is formally or primarily aligned.
-
B.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
-
C.
hasProtagonistGroup
Indicates that a narrative work features a central group of characters who collectively serve as the main protagonists.
-
D.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
E.
hasAntagonistGroup
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb11230b881908f5b554323729cc5 |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.