Triple
T27088483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridgerton |
E686097
|
entity |
| Predicate | castingCharacteristic |
P141905
|
FINISHED |
| Object | diverse casting |
—
|
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: diverse casting | Statement: [Bridgerton, castingCharacteristic, diverse casting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castingCharacteristic Context triple: [Bridgerton, castingCharacteristic, diverse casting]
-
A.
castFeature
Indicates that a particular actor or performer is part of the cast for a given feature (such as a film, show, or other production).
-
B.
castingNote
Indicates that there is an explanatory note or comment about how a role was cast or performed in a production.
-
C.
cast
Indicates that an agent selects and assigns a person or thing to play a specific role or function in a production or context.
-
D.
castCharacteristic
chosen
Indicates that a particular characteristic or attribute is associated with, or defines, a cast or group of performers.
-
E.
castingReason
Indicates the reason or justification for selecting or assigning a particular entity (e.g., a person or object) to a specific role, function, or category.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623480110819088369af135123c24 |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:39 a.m.