Triple
T11659486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elytra |
E277085
|
entity |
| Predicate | canPrevent |
P43618
|
FINISHED |
| Object | fall damage if used correctly |
—
|
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: fall damage if used correctly | Statement: [Elytra, canPrevent, fall damage if used correctly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canPrevent Context triple: [Elytra, canPrevent, fall damage if used correctly]
-
A.
isPreventableBy
Indicates that the occurrence or effect of one entity can be avoided or stopped through the action, intervention, or influence of another entity.
-
B.
canPerform
Indicates that one entity has the ability, permission, or capacity to carry out a specific action or function on or with another entity.
-
C.
canSuppress
Indicates that one entity has the ability or capacity to prevent, inhibit, or reduce the effect, activity, or expression of another entity or process.
-
D.
prevented
Indicates that one entity stopped, hindered, or made it impossible for another entity or event to occur or proceed.
-
E.
canBlock
chosen
Indicates that one entity has the ability or permission to prevent, obstruct, or stop the action or effect 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.