Triple
T38120341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Aster |
E951913
|
entity |
| Predicate | hasDramaticRole |
P104626
|
FINISHED |
| Object | supporting protagonist |
—
|
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: supporting protagonist | Statement: [Lord Aster, hasDramaticRole, supporting protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDramaticRole Context triple: [Lord Aster, hasDramaticRole, supporting protagonist]
-
A.
dramaticRole
Indicates that one entity serves as a character or part played by another entity within a dramatic or theatrical work.
-
B.
playedEarlyRoleIn
Indicates that one entity contributed significantly to the initial or formative stages of another entity’s development, success, or emergence.
-
C.
hasPortrayedRole
chosen
Indicates that an entity has performed or depicted a specific role or character, typically in a work such as a film, play, or television show.
-
D.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
-
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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.