Triple
T22123466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Phantom of the Range |
E546731
|
entity |
| Predicate | hasCastMemberGenderDiversity |
P81870
|
FINISHED |
| Object | includes female actors |
—
|
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: includes female actors | Statement: [The Phantom of the Range, hasCastMemberGenderDiversity, includes female actors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCastMemberGenderDiversity Context triple: [The Phantom of the Range, hasCastMemberGenderDiversity, includes female actors]
-
A.
hasPerformerGenderComposition
chosen
Indicates the gender makeup of the group of performers involved in an event or performance.
-
B.
hasDirectorGender
Indicates that an entity has a director whose gender is specified by the related value.
-
C.
hasGenderRepresentation
Indicates that something includes, reflects, or portrays one or more genders within its content, structure, or composition.
-
D.
hasLeadCharacterGender
Indicates that the primary or lead character in a work has a specified gender.
-
E.
hasPerformerGender
Indicates that an action, event, or performance is associated with the gender of the performer who carries it out.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1297f3fb48190b6aaca18b40c37ab |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.