Triple
T11694272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundle of Joy |
E277950
|
entity |
| Predicate | leadActressCharacterType |
P16411
|
FINISHED |
| Object | unmarried salesgirl |
—
|
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: unmarried salesgirl | Statement: [Bundle of Joy, leadActressCharacterType, unmarried salesgirl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActressCharacterType Context triple: [Bundle of Joy, leadActressCharacterType, unmarried salesgirl]
-
A.
leadActress
Indicates that the subject is the primary female performer in the specified film, show, or production.
-
B.
actingRoleType
chosen
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
-
C.
characterPortrayedIs
Indicates that one entity serves as the fictional or dramatic role that is depicted or played by another entity.
-
D.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
E.
replacesInLeadRole
Indicates that one entity takes over or substitutes for another entity in the primary or leading role within a given context or production.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47b9eb48190976a35e91e25b56b |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.