Triple
T26769707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drottningänka |
E675044
|
entity |
| Predicate | appliesToSpouseOf |
P113199
|
FINISHED |
| Object | deceased king of Sweden |
—
|
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: deceased king of Sweden | Statement: [Drottningänka, appliesToSpouseOf, deceased king of Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToSpouseOf Context triple: [Drottningänka, appliesToSpouseOf, deceased king of Sweden]
-
A.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
B.
associatedWithFieldThroughSpouse
Indicates that an entity is connected to a particular field or domain by virtue of their spouse’s involvement or association with that field.
-
C.
throughSpouse
chosen
Indicates a relationship or connection that exists indirectly between two entities by way of one entity’s spouse.
-
D.
spouseOfInstanceOf
Indicates that one entity is the spouse of another entity that is an instance of a specified class or type.
-
E.
spouseRelative
Indicates that one person is related to another through the marriage of at least one of them (e.g., in-laws or relatives by marriage).
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 27, 2026, 4:01 a.m.