Triple
T1373156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke |
E30157
|
entity |
| Predicate | mayBeRoyalTitle |
P17683
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Duke, mayBeRoyalTitle, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeRoyalTitle Context triple: [Duke, mayBeRoyalTitle, yes]
-
A.
isRoyalTitle
chosen
Indicates that something is a formal title associated with royalty or a royal rank.
-
B.
representativeOfMonarchTitle
Indicates that one entity serves as the official representative or holder of authority on behalf of a monarch’s title.
-
C.
hasHeirApparentTitle
Indicates that an entity holds a title designating them as the officially recognized heir apparent to another entity’s position or rank.
-
D.
hasPatronalTitle
Indicates that an entity holds or is associated with a specific patronal or honorific title, typically reflecting patronage, protection, or dedication.
-
E.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2f4889881908103473a0173e23f |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.