Triple
T20408332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deryck Whibley |
E500526
|
entity |
| Predicate | startTimeSpouse |
P67588
|
FINISHED |
| Object | 2006-07-15 |
—
|
LITERAL FINISHED |
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: 2006-07-15 | Statement: [Deryck Whibley, startTimeSpouse, 2006-07-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeSpouse Context triple: [Deryck Whibley, startTimeSpouse, 2006-07-15]
-
A.
spouseStartTime
Indicates the point in time when two individuals began their spousal (marriage) relationship.
-
B.
spouseEndTime
Indicates the time or date at which a spousal relationship between two entities ends.
-
C.
metSpouseAt
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
D.
spouseOfSince
chosen
Indicates that two individuals are spouses and specifies the date or time from which their marital relationship has been in effect.
-
E.
spousePositionHeldStartTime
Indicates the date and time when a spouse first began holding a particular position or office.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a3d03ac81908f37b907ccbb5088 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.