Triple
T32042127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Decoy Bride |
E818243
|
entity |
| Predicate | featuresWedding |
P80690
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [The Decoy Bride, featuresWedding, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresWedding Context triple: [The Decoy Bride, featuresWedding, Yes]
-
A.
weddingPart
Indicates that an entity participates as a component or role within a wedding event.
-
B.
featuresDecor
Indicates that one entity includes or showcases the decor elements provided or defined by another entity.
-
C.
weddingDescribedAs
Indicates that a particular wedding is characterized or portrayed using a specific description or label.
-
D.
weddingBehavior
Indicates behavior, actions, or customs that occur specifically in the context of a wedding or wedding-related events.
-
E.
featuresIn
chosen
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00af6b3a948190a92813c13384c304 |
completed | May 10, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_6a00aec35610819085dd5137715a4228 |
completed | May 10, 2026, 4:13 p.m. |
Created at: May 1, 2026, 12:19 a.m.