Triple
T4268489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Generalísimo |
E96881
|
entity |
| Predicate | usedAsTitle |
P9146
|
FINISHED |
| Object | honorific for supreme commander |
—
|
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: honorific for supreme commander | Statement: [Generalísimo, usedAsTitle, honorific for supreme commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTitle Context triple: [Generalísimo, usedAsTitle, honorific for supreme commander]
-
A.
usedAsTitleInFull
Indicates that something functions as a formal title within the complete, official version of a name or designation.
-
B.
usedAsTitleBeforeName
chosen
Indicates that a term or phrase functions as a formal title placed immediately before a person's name.
-
C.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
D.
titleUsage
Indicates how a title is applied, referenced, or used in relation to an entity or context.
-
E.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ff913608190b6ccf4a85057b07b |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.