Triple
T15443455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Ducal Serene Highness |
E369966
|
entity |
| Predicate | containsTitleElement |
P103300
|
FINISHED |
| Object | Ducal |
—
|
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: Ducal | Statement: [His Ducal Serene Highness, containsTitleElement, Ducal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTitleElement Context triple: [His Ducal Serene Highness, containsTitleElement, Ducal]
-
A.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
D.
hasTitleRole
Indicates that an entity holds or is assigned a specific title or role in relation to another entity.
-
E.
hasTitleFeature
chosen
Indicates that an entity possesses a specific characteristic, attribute, or element related to its 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef55f5c8190a32b1b6ad1daf454 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.