Triple
T28921037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lily Savage |
E733511
|
entity |
| Predicate | realLifePerformerGender |
P20803
|
FINISHED |
| Object | male |
—
|
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: male | Statement: [Lily Savage, realLifePerformerGender, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realLifePerformerGender Context triple: [Lily Savage, realLifePerformerGender, male]
-
A.
hasPerformerGender
chosen
Indicates that an action, event, or performance is associated with the gender of the performer who carries it out.
-
B.
realWorldPerformer
Indicates that an entity serves as the actual, real-world performer of an action, role, or content represented in another entity.
-
C.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
D.
livePerformer
Indicates that an entity performs an artistic or entertainment act live, typically in front of an audience.
-
E.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
- 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.