Triple
T28921332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lily Savage |
E733519
|
entity |
| Predicate | sexualOrientationOfPerformer |
P4324
|
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: [Lily Savage, sexualOrientationOfPerformer, gay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sexualOrientationOfPerformer Context triple: [Lily Savage, sexualOrientationOfPerformer, gay]
-
A.
sexualOrientation
chosen
Indicates an entity’s enduring pattern of romantic or sexual attraction toward others, typically in terms of the genders or sexes to which it is attracted.
-
B.
sexualOrientationRevealedIn
Indicates that an entity’s sexual orientation is disclosed, made known, or becomes apparent within a specified context, medium, or situation.
-
C.
leadActorSexualOrientation
Indicates the sexual orientation of the lead actor in a work or production.
-
D.
hasPerformerGender
Indicates that an action, event, or performance is associated with the gender of the performer who carries it out.
-
E.
creatorSexOrGender
Indicates that the specified sex or gender is the sex or gender of the creator of the referenced work or entity.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b1b09a08190934a1b04d6381028 |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:19 a.m.