Triple
T8401897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan de Cartagena |
E198391
|
entity |
| Predicate | mutinyRole |
P59854
|
FINISHED |
| Object | co-leader of the mutiny at Puerto San Julián |
—
|
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: co-leader of the mutiny at Puerto San Julián | Statement: [Juan de Cartagena, mutinyRole, co-leader of the mutiny at Puerto San Julián]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mutinyRole Context triple: [Juan de Cartagena, mutinyRole, co-leader of the mutiny at Puerto San Julián]
-
A.
roleInMutiny
chosen
Indicates that one entity participated in a mutiny with a specific role or capacity in that rebellious action.
-
B.
typeOfRebel
Indicates that one entity is a rebel belonging to, or classified under, a particular type or category of rebellion.
-
C.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
D.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
E.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
- 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb824efa5c81908ce816cdb8e1fcfb |
completed | March 31, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:04 p.m.