Triple
T34015903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Womack & Womack |
E872240
|
entity |
| Predicate | spousesInDuo |
P167725
|
FINISHED |
| Object | Cecil Womack and Linda Womack |
—
|
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: Cecil Womack and Linda Womack | Statement: [Womack & Womack, spousesInDuo, Cecil Womack and Linda Womack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spousesInDuo Context triple: [Womack & Womack, spousesInDuo, Cecil Womack and Linda Womack]
-
A.
spouseInDuo
chosen
Indicates that two individuals are spouses who perform or appear together as a duo.
-
B.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
C.
spouseIn
Indicates that one entity is the spouse (married partner) of another entity within a specified context or grouping.
-
D.
spouseOfSequence
Indicates a sequential or ordered relationship of being spouses, where each entity is married to the next in the sequence.
-
E.
marriedCouple
Indicates that two individuals are legally and/or socially recognized as being married to each other as a couple.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:51 a.m.