Triple
T38120711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ladies in Waiting |
E951924
|
entity |
| Predicate | playsForCharacters |
P191743
|
FINISHED |
| Object | six wives of Henry VIII |
—
|
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: six wives of Henry VIII | Statement: [The Ladies in Waiting, playsForCharacters, six wives of Henry VIII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsForCharacters Context triple: [The Ladies in Waiting, playsForCharacters, six wives of Henry VIII]
-
A.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
B.
worksForCharacterPlayedBy
Indicates that one character is employed by, or works under, another character who is portrayed by a specific actor.
-
C.
playsAs
Indicates that one entity performs, portrays, or assumes the role, character, or persona of another entity.
-
D.
arePlayedBy
Indicates that one or more performers (such as actors or musicians) carry out, interpret, or execute the referenced roles, characters, or pieces.
-
E.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:21 p.m.