Triple
T11082169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornelia Bell |
E262025
|
entity |
| Predicate | spouseSignificantEvent |
P85988
|
FINISHED |
| Object | signer of the United States Constitution |
—
|
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: signer of the United States Constitution | Statement: [Cornelia Bell, spouseSignificantEvent, signer of the United States Constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseSignificantEvent Context triple: [Cornelia Bell, spouseSignificantEvent, signer of the United States Constitution]
-
A.
partnerInLifeEvent
Indicates that two or more entities share a partnership or joint involvement in a specific life event or milestone.
-
B.
hasSpouseNotableEvent
chosen
Indicates that a person’s spouse is associated with a notable event related to that person.
-
C.
spouseAtEvent
Indicates that two individuals are spouses who are present together at a specific event.
-
D.
spouseOfNotableEvent
Indicates a marital relationship where one spouse is a notable event or is contextually defined through association with a notable event.
-
E.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799985650819089b2c0f35a212414 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.