Triple
T28845723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indefinite Divisibility |
E728447
|
entity |
| Predicate | creatorSpouseAtTime |
P181432
|
FINISHED |
| Object | Kay Sage |
—
|
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: Kay Sage | Statement: [Indefinite Divisibility, creatorSpouseAtTime, Kay Sage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorSpouseAtTime Context triple: [Indefinite Divisibility, creatorSpouseAtTime, Kay Sage]
-
A.
subjectSpouseAtTime
chosen
Indicates that the subject is married to a specified spouse during a particular time period.
-
B.
hasAuthorSpouse
Indicates that the spouse of the subject entity is the author of the related work or entity.
-
C.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
D.
spouseOfSince
Indicates that two individuals are spouses and specifies the date or time from which their marital relationship has been in effect.
-
E.
composerSpouse
Indicates that one person is the spouse (married partner) of a composer.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 28, 2026, 6:42 a.m.