Triple
T22200190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Kennington |
E548658
|
entity |
| Predicate | titleHolderRoyalStatus |
P41897
|
FINISHED |
| Object | British prince |
—
|
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: British prince | Statement: [Earl of Kennington, titleHolderRoyalStatus, British prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderRoyalStatus Context triple: [Earl of Kennington, titleHolderRoyalStatus, British prince]
-
A.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
B.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
C.
titleHolderIs
chosen
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
D.
royalTitularyFeature
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
-
E.
titleHolderOfficeBeforePeerage
Indicates that the person holding a title previously held a specific office before being elevated to the peerage.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aea51d48190a570cd36c106ab78 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.