Triple
T11678471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Men |
E277552
|
entity |
| Predicate | leadCharacterDisability |
P148
|
FINISHED |
| Object | paraplegia |
—
|
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: paraplegia | Statement: [The Men, leadCharacterDisability, paraplegia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadCharacterDisability Context triple: [The Men, leadCharacterDisability, paraplegia]
-
A.
hasDisabilityRepresentation
Indicates that something includes, portrays, or accounts for the presence and experiences of people with disabilities.
-
B.
causeOfDisability
Indicates that one entity is the reason or source that brings about another entity’s disability.
-
C.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
D.
disability
chosen
Indicates that an entity has a physical, mental, or sensory impairment that substantially limits one or more major life activities.
-
E.
leadCharacterActivity
Indicates that an activity is performed by, associated with, or characteristic of the lead character in a narrative or work.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a46000a48190888ad1a6ade052e3 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.