Triple
T20391277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Dekker |
E498088
|
entity |
| Predicate | hasPubliclyComeOutAs |
P40086
|
FINISHED |
| Object | 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: gay | Statement: [Thomas Dekker, hasPubliclyComeOutAs, gay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPubliclyComeOutAs Context triple: [Thomas Dekker, hasPubliclyComeOutAs, gay]
-
A.
publiclyCameOutAsTransgender
Indicates that a person has openly and publicly disclosed that they are transgender.
-
B.
publiclyIdentifiesAs
Indicates that an entity openly declares or presents themself to others as having a particular identity or role.
-
C.
isOpenlyLGBT
chosen
Indicates that an entity publicly identifies as lesbian, gay, bisexual, transgender, or otherwise part of the LGBT community.
-
D.
hasPublicFigure
Indicates that an entity is associated with or characterized by a specific public figure, such as a celebrity, politician, or other widely recognized individual.
-
E.
sexualOrientationRevealedIn
Indicates that an entity’s sexual orientation is disclosed, made known, or becomes apparent within a specified context, medium, or situation.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790f8d9c819093038f6bb6f47a92 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:28 a.m.