Triple
T21481313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emily Montgomery |
E529999
|
entity |
| Predicate | weddingDisruptedBy |
P105676
|
FINISHED |
| Object | Howard Brackett being outed as gay |
—
|
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: Howard Brackett being outed as gay | Statement: [Emily Montgomery, weddingDisruptedBy, Howard Brackett being outed as gay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weddingDisruptedBy Context triple: [Emily Montgomery, weddingDisruptedBy, Howard Brackett being outed as gay]
-
A.
brideMistakenAs
Indicates that one person is incorrectly identified or perceived as a bride instead of the actual intended bride.
-
B.
disruptedIn
chosen
Indicates that a normal process, function, or state is interrupted, impaired, or thrown into disorder within the specified context.
-
C.
functionDuringWedding
Indicates that an entity performs a specific role or function in the context of a wedding event.
-
D.
associatedWithWeddingOf
Indicates a relationship where something is connected or related to the wedding event of specific individuals.
-
E.
nuptialFlightTrigger
Indicates the condition or event that initiates or triggers a nuptial flight between mating individuals.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea338f988190a3044f8d02a567fe |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:21 p.m.