Triple
T20358510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De nobilitate |
E496713
|
entity |
| Predicate | positionOnNobility |
P139814
|
FINISHED |
| Object | emphasizes personal virtue over birth |
—
|
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: emphasizes personal virtue over birth | Statement: [De nobilitate, positionOnNobility, emphasizes personal virtue over birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnNobility Context triple: [De nobilitate, positionOnNobility, emphasizes personal virtue over birth]
-
A.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
B.
parentalNobilityRank
Indicates the comparative social or noble status level held by a subject’s parent(s) within a hierarchy of nobility.
-
C.
nobleRankInHierarchy
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
-
D.
nobilitySystem
Indicates a social or political structure in which individuals are ranked by hereditary titles or noble status.
-
E.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
- F. None of above. chosen
Provenance (4 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67855c3a88190b88839a47d01184d |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:25 a.m.