Triple
T22637612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Villahermosa |
E558722
|
entity |
| Predicate | aristocraticInfluence |
P106712
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [House of Villahermosa, aristocraticInfluence, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aristocraticInfluence Context triple: [House of Villahermosa, aristocraticInfluence, high]
-
A.
aristocraticContext
Indicates that the relationship or action occurs within, is shaped by, or is characteristic of an aristocratic or noble social context.
-
B.
stanceOnAristocracy
Indicates a subject's expressed attitude, position, or viewpoint regarding aristocracy as a social or political system.
-
C.
aristocraticStyle
Indicates a relationship where something exhibits or embodies the manner, tastes, or aesthetic typically associated with aristocracy or the aristocratic class.
-
D.
aristocraticRole
Indicates that an entity holds or is associated with a formal position, title, or function within an aristocratic or noble hierarchy.
-
E.
nobleHouseInfluence
chosen
Indicates the degree to which a noble house exerts power, control, or sway over people, events, or territories.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1700edb608190ad786ff7fafea0da |
completed | April 29, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:03 p.m.