Triple
T29295376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patricia Blum |
E742812
|
entity |
| Predicate | marriedToInStory |
P30304
|
FINISHED |
| Object | Stan Uris |
—
|
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: Stan Uris | Statement: [Patricia Blum, marriedToInStory, Stan Uris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedToInStory Context triple: [Patricia Blum, marriedToInStory, Stan Uris]
-
A.
hasSpouseInStory
chosen
Indicates that one entity is depicted as the spouse of another within the context of a particular story or narrative.
-
B.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
C.
marriedIn
Indicates that two entities entered into a marital relationship at a specific place or within a particular jurisdiction.
-
D.
laterMarriedIn
Indicates that two entities became married at a later time relative to a previously referenced event or marital status.
-
E.
resultedInMarriageTo
Indicates that one event, action, or circumstance led to or caused a marriage to occur between the related 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 28, 2026, 1:05 p.m.