Triple
T15308329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrait of the Duke of Burgundy |
E365961
|
entity |
| Predicate | portrayedPersonNobilityStatus |
P52082
|
FINISHED |
| Object | aristocrat |
—
|
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: aristocrat | Statement: [Portrait of the Duke of Burgundy, portrayedPersonNobilityStatus, aristocrat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedPersonNobilityStatus Context triple: [Portrait of the Duke of Burgundy, portrayedPersonNobilityStatus, aristocrat]
-
A.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
B.
hasNobleStatus
chosen
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
C.
aristocraticTitleStatus
Indicates the status or condition of an entity’s aristocratic or noble title (e.g., whether and how the title is held, recognized, or used).
-
D.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
E.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd001b48190bbdd69337efdb907 |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.