Triple
T25183236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cormac Wibberley |
E630641
|
entity |
| Predicate | marriedToCollaborator |
P21331
|
FINISHED |
| Object | Marianne Wibberley |
—
|
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: Marianne Wibberley | Statement: [Cormac Wibberley, marriedToCollaborator, Marianne Wibberley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedToCollaborator Context triple: [Cormac Wibberley, marriedToCollaborator, Marianne Wibberley]
-
A.
hasCollaborativeRoleWithSpouse
Indicates that an individual shares a joint, cooperative role or responsibility together with their spouse.
-
B.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
C.
coSpouse
chosen
Indicates that two individuals are married to each other as spouses.
-
D.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
-
E.
partnerInUnionWith
Indicates a mutual partnership or union relationship between two entities, such as a civil, domestic, or similar legally or socially recognized union.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 21, 2026, 12:36 p.m.