Triple
T16073405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baronetage of England |
E389921
|
entity |
| Predicate | spouseStyle |
P121784
|
FINISHED |
| Object | Lady |
—
|
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: Lady | Statement: [Baronetage of England, spouseStyle, Lady]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseStyle Context triple: [Baronetage of England, spouseStyle, Lady]
-
A.
hasSpouseStyle
Indicates a relationship where one entity’s manner, appearance, or behavior resembles or is characteristic of another entity’s spouse.
-
B.
spouseWritingStyle
Indicates that one person’s writing style is influenced by, similar to, or characterized in relation to their spouse’s writing style.
-
C.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
D.
spouseCharacteristic
Indicates that a particular characteristic, trait, or attribute is associated with a person’s spouse within the relationship.
-
E.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:57 a.m.