Triple
T1905956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Duke |
E38004
|
entity |
| Predicate | claimsNobility |
P5052
|
FINISHED |
| Object | European aristocracy |
—
|
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: European aristocracy | Statement: [The Duke, claimsNobility, European aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsNobility Context triple: [The Duke, claimsNobility, European aristocracy]
-
A.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
B.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
C.
dynasticClaim
Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
-
D.
claimedTitle
chosen
Indicates that an entity asserts or declares possession of a particular title or rank.
-
E.
headOfNobleFamily
Indicates that one entity holds the position of leader or chief authority over a particular noble family.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.