Triple
T10492940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Of Human Bondage (1946 film) |
E247462
|
entity |
| Predicate | mainCharacterDisability |
P93885
|
FINISHED |
| Object | clubfoot |
—
|
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: clubfoot | Statement: [Of Human Bondage (1946 film), mainCharacterDisability, clubfoot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterDisability Context triple: [Of Human Bondage (1946 film), mainCharacterDisability, clubfoot]
-
A.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
B.
usesCharacter
Indicates that one entity employs, incorporates, or relies on a particular character (such as a symbol, letter, or persona) in its form, function, or representation.
-
C.
isPivotalForCharacter
Indicates that something plays a crucial, defining role in shaping a character’s development, decisions, or narrative arc.
-
D.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
E.
hasProtagonistCondition
chosen
Indicates that the main character in a narrative has a particular condition, state, or affliction.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097ecbec8190807c4fcc85662026 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:24 p.m.