Triple
T4501232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Omnium |
E101223
|
entity |
| Predicate | nobleTitleInFiction |
P914
|
FINISHED |
| Object | British peer |
—
|
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 peer | Statement: [Duke of Omnium, nobleTitleInFiction, British peer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleInFiction Context triple: [Duke of Omnium, nobleTitleInFiction, British peer]
-
A.
nobleTitleFrom
Indicates that a person derives or holds their noble title from a specified source, such as a place, lineage, or authority.
-
B.
associatedNobleTitle
chosen
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
C.
nobleTitleNumber
Indicates the ordinal number or sequence position associated with a person's noble title (e.g., first duke, second baron).
-
D.
epithetOrTitle
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
-
E.
representativeOfMonarchTitle
Indicates that one entity serves as the official representative or holder of authority on behalf of a monarch’s 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56f9dca08190b926f40e201a3e97 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.