Triple
T11659474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elytra |
E277085
|
entity |
| Predicate | durabilityLossRate |
P100805
|
FINISHED |
| Object | 1 durability per second of gliding |
—
|
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: 1 durability per second of gliding | Statement: [Elytra, durabilityLossRate, 1 durability per second of gliding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: durabilityLossRate Context triple: [Elytra, durabilityLossRate, 1 durability per second of gliding]
-
A.
durabilityClass
Indicates the level or category of resistance an entity has to wear, damage, or degradation over time.
-
B.
massLossRate
Indicates the rate at which an object or system is losing mass over time.
-
C.
mechanicalDurability
Indicates the ability of something to withstand mechanical forces, stresses, or wear without failing or degrading.
-
D.
preservationFactor
Indicates the degree to which something is protected, maintained, or kept intact over time, often moderating how much change, loss, or degradation occurs.
-
E.
canBeLostBy
Indicates that something is capable of being lost or forfeited by a particular entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:39 p.m.