Triple
T32910185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marian von Schraft |
E841852
|
entity |
| Predicate | laterMarriedNameOf |
P99359
|
FINISHED |
| Object | Marian Marsh |
—
|
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: Marian Marsh | Statement: [Marian von Schraft, laterMarriedNameOf, Marian Marsh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterMarriedNameOf Context triple: [Marian von Schraft, laterMarriedNameOf, Marian Marsh]
-
A.
laterMarriedName
chosen
Indicates that the referenced name is a surname or full name a person adopted after a later marriage, replacing or succeeding their previous name.
-
B.
laterMarriedBy
Indicates that an entity is married by another entity at a later point in time relative to some prior reference event or relationship.
-
C.
laterMarriedIn
Indicates that two entities became married at a later time relative to a previously referenced event or marital status.
-
D.
eraNameOfSpouse
Indicates that the value is the name of the historical era associated with the spouse of the subject.
-
E.
spouseLaterMarriedBy
Indicates that one’s spouse subsequently entered into a later marriage with another partner.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: May 1, 2026, 1:19 a.m.