Triple
T24646857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Piedmont |
E610135
|
entity |
| Predicate | styleOftenHeldWith |
P156903
|
FINISHED |
| Object | Her Royal Highness |
—
|
NE NERFINISHED |
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: Her Royal Highness | Statement: [Princess of Piedmont, styleOftenHeldWith, Her Royal Highness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOftenHeldWith Context triple: [Princess of Piedmont, styleOftenHeldWith, Her Royal Highness]
-
A.
oftenHeldWith
Indicates that one entity is frequently possessed, carried, or kept together with another entity at the same time.
-
B.
oftenHeldAs
Indicates that one entity is frequently regarded, considered, or believed to be in a particular way with respect to another entity or property.
-
C.
styleHeldBy
Indicates that a particular style, design, or aesthetic is possessed, used, or embodied by a specific entity.
-
D.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
-
E.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f41010f06c81908ee7f773220df14f |
completed | May 1, 2026, 2:29 a.m. |
Created at: April 18, 2026, 2:33 a.m.