Triple
T2200874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperator Furiosa |
E50484
|
entity |
| Predicate | usesProsthetic |
P2728
|
FINISHED |
| Object | mechanical 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: mechanical arm | Statement: [Imperator Furiosa, usesProsthetic, mechanical arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProsthetic Context triple: [Imperator Furiosa, usesProsthetic, mechanical arm]
-
A.
usesEquipment
chosen
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
B.
usesModality
Indicates that an action, communication, or process is carried out through or characterized by a particular modality (such as visual, auditory, tactile, or another mode of expression or operation).
-
C.
usedByPerson
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
-
D.
hasArms
Indicates that an entity possesses arms as physical appendages.
-
E.
wearAuthorizedBy
Indicates that one entity’s wearing or use of an item (such as clothing, uniform, or equipment) is permitted or approved by 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.