Triple
T31703671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Irulan |
E809123
|
entity |
| Predicate | spouseOfConvenience |
P194259
|
FINISHED |
| Object | Paul Atreides |
—
|
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: Paul Atreides | Statement: [Princess Irulan, spouseOfConvenience, Paul Atreides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfConvenience Context triple: [Princess Irulan, spouseOfConvenience, Paul Atreides]
-
A.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
B.
spouseIn
Indicates that one entity is the spouse (married partner) of another entity within a specified context or grouping.
-
C.
forcedSpouse
Indicates a marital relationship in which at least one spouse was compelled or coerced into the marriage against their will.
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
coSpouse
Indicates that two individuals are married to each other as spouses.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: April 30, 2026, 11:13 p.m.