Triple
T12997386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hailie Sahar |
E322074
|
entity |
| Predicate | publicIdentity |
P107751
|
FINISHED |
| Object | openly transgender actress |
—
|
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: openly transgender actress | Statement: [Hailie Sahar, publicIdentity, openly transgender actress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicIdentity Context triple: [Hailie Sahar, publicIdentity, openly transgender actress]
-
A.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
-
B.
adoptedIdentity
Indicates that one entity has taken on or assumed the identity, role, or persona of another entity, either formally or informally.
-
C.
localIdentity
Indicates that an entity’s identity or role is defined specifically within a particular local context, scope, or environment, rather than globally.
-
D.
identityRevealedIn
Indicates that an entity’s true identity becomes known or disclosed within a specified context, source, or situation.
-
E.
standardIdentity
Indicates that two entities are considered equivalent or identical according to a defined standard or canonical form.
- F. None of above. chosen
Provenance (4 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e7980288190a9fe629a8cc76a52 |
completed | April 10, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e74283c819082e69ac3554fa7d8 |
completed | April 10, 2026, 10:49 p.m. |
Created at: April 9, 2026, 8:45 p.m.