Triple
T24751461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captaincy General of Santo Domingo |
E619154
|
entity |
| Predicate | militaryLeaderTitle |
P2084
|
FINISHED |
| Object | captain general |
—
|
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: captain general | Statement: [Captaincy General of Santo Domingo, militaryLeaderTitle, captain general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryLeaderTitle Context triple: [Captaincy General of Santo Domingo, militaryLeaderTitle, captain general]
-
A.
militaryLeader
Indicates that one entity serves as the commanding military leader of another entity, such as a state, organization, or armed force.
-
B.
commanderTitle
chosen
Indicates the official rank or title held by the person who commands or leads a given entity.
-
C.
civilianLeaderTitle
Indicates the official title held by a person who serves as the civilian leader of a group, organization, or jurisdiction.
-
D.
laterTitleOfCommander
Indicates that one title represents a later-held command position of the same commander who previously held another title.
-
E.
seniorEnlistedLeaderTitle
Indicates the formal title held by the senior enlisted leader in a military or similar hierarchical organization.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:25 a.m.