Triple
T33474313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer Roberts |
E857276
|
entity |
| Predicate | wedding |
P43279
|
FINISHED |
| Object | marries Seth Cohen in series finale |
—
|
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: marries Seth Cohen in series finale | Statement: [Summer Roberts, wedding, marries Seth Cohen in series finale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wedding Context triple: [Summer Roberts, wedding, marries Seth Cohen in series finale]
-
A.
weddingPart
Indicates that an entity participates as a component or role within a wedding event.
-
B.
bride
chosen
Indicates that an entity is a woman who is getting married or has just been married in relation to a wedding event or spouse.
-
C.
weddingStatus
Indicates the current state or condition of an entity’s marriage or wedding (e.g., single, engaged, married, divorced).
-
D.
associatedWithWeddingOf
Indicates a relationship where something is connected or related to the wedding event of specific individuals.
-
E.
weddingRole
Indicates the specific role or function an entity has in the context of a wedding event.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e501c1fc819081b14287930e834d |
completed | May 3, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.