Triple
T37661645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eye of Ender |
E937729
|
entity |
| Predicate | breakChancePerUse |
P70746
|
FINISHED |
| Object | 0.2 |
—
|
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: 0.2 | Statement: [Eye of Ender, breakChancePerUse, 0.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakChancePerUse Context triple: [Eye of Ender, breakChancePerUse, 0.2]
-
A.
failureRate
Indicates the proportion or frequency at which a system, component, or process fails over a specified set of operations or time period.
-
B.
hasFailureProbability
chosen
Indicates that an entity is associated with a likelihood or chance that it will fail within a given context or conditions.
-
C.
brokenUsing
Indicates that one entity was broken or damaged through the use or application of another entity as the means or tool.
-
D.
loserPercentage
Indicates the proportion of entities in a group that have lost or failed according to a specified criterion.
-
E.
willBreakFreeDuring
Indicates that an entity is expected to escape or become free from another entity or constraint during a specified time or event.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.