Triple
T2200873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperator Furiosa |
E50484
|
entity |
| Predicate | hasPhysicalDisability |
P148
|
FINISHED |
| Object | missing left arm |
—
|
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: missing left arm | Statement: [Imperator Furiosa, hasPhysicalDisability, missing left arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalDisability Context triple: [Imperator Furiosa, hasPhysicalDisability, missing left arm]
-
A.
causeOfDisability
Indicates that one entity is the reason or source that brings about another entity’s disability.
-
B.
disability
chosen
Indicates that an entity has a physical, mental, or sensory impairment that substantially limits one or more major life activities.
-
C.
canImpair
Indicates that one entity has the potential or ability to weaken, damage, or reduce the normal function, quality, or effectiveness of another entity.
-
D.
hasDisabledAccess
Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
-
E.
hasPhysicalFeature
Indicates that one entity possesses or exhibits a specific physical characteristic or feature of another entity.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa06bb4819092d7021358846e5f |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.