Triple
T17656467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claude Rains |
E429639
|
entity |
| Predicate | spouseOrdinalRosemaryClarkSchrode |
P128416
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Claude Rains, spouseOrdinalRosemaryClarkSchrode, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOrdinalRosemaryClarkSchrode Context triple: [Claude Rains, spouseOrdinalRosemaryClarkSchrode, 3]
-
A.
spouseAlsoKnownAs
Indicates that a person’s spouse is referred to by an alternative name or alias.
-
B.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
C.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
-
D.
sometimesSpouseOf
Indicates that two entities are occasionally, but not consistently or permanently, in a spousal relationship with each other.
-
E.
spouseOfRole
Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46ea2b3308190b9ad752728d98856 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 6:06 a.m.