Triple
T20932588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimson Gold |
E515504
|
entity |
| Predicate | usesCastType |
P69823
|
FINISHED |
| Object | non-professional 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: non-professional actors | Statement: [Crimson Gold, usesCastType, non-professional actors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCastType Context triple: [Crimson Gold, usesCastType, non-professional actors]
-
A.
hasCastType
chosen
Indicates that an entity participates in a production with a specified type of casting role (e.g., lead, supporting, cameo).
-
B.
usesCastingOf
Indicates that one entity employs or applies a particular casting of another entity (such as a type, role, or form) in its operation or context.
-
C.
castingType
Indicates the specific method or category of casting used to transform or represent one entity in terms of another.
-
D.
isTypecast
Indicates that an entity has been assigned or converted to a different type or role than its original or natural one.
-
E.
oftenCastAs
Indicates that one entity is frequently assigned or chosen to play a particular role, type, or character in performances or representations.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f94e980c819083280a9c35af5930 |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.