Triple
T32136930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonio Bologna |
E820790
|
entity |
| Predicate | relationshipToDuchess |
P206193
|
FINISHED |
| Object | steward |
—
|
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: steward | Statement: [Antonio Bologna, relationshipToDuchess, steward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToDuchess Context triple: [Antonio Bologna, relationshipToDuchess, steward]
-
A.
relationshipWithDukes
Indicates that an entity has a specified type of relationship or association with one or more dukes.
-
B.
relationshipToPrincess
Indicates the specific familial, social, or romantic connection that one entity has to a princess.
-
C.
relationshipToQueenOfHearts
Indicates the specific familial, social, or hierarchical relationship that one entity has to the Queen of Hearts.
-
D.
reignAsDuchessTo
Indicates that one entity holds and exercises the title and authority of duchess in relation to another specified domain, territory, or noble house.
-
E.
relationshipToCatherine
Indicates the specific familial, social, or interpersonal connection that one entity has to the person named Catherine.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:30 a.m.