Triple
T6228912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elliot Page |
E139302
|
entity |
| Predicate | publicAnnouncement |
P4650
|
FINISHED |
| Object | came out as gay in 2014 |
—
|
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: came out as gay in 2014 | Statement: [Elliot Page, publicAnnouncement, came out as gay in 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicAnnouncement Context triple: [Elliot Page, publicAnnouncement, came out as gay in 2014]
-
A.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
-
B.
announcedThat
chosen
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
C.
announcementFormula
Indicates that one entity is the formal content or wording used in an announcement made by another entity.
-
D.
typicalAnnouncementContext
Indicates that an announcement occurs in a context or situation that is considered typical or characteristic for such announcements.
-
E.
primaryAnnouncer
Indicates that an entity serves as the main or lead announcer in a given event, program, 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062d841a88190b67a8045cdaadf44 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.