Triple
T37456990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fireblast |
E930823
|
entity |
| Predicate | usageLimitPerTurn |
P149053
|
FINISHED |
| Object | Once by default |
—
|
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: Once by default | Statement: [Fireblast, usageLimitPerTurn, Once by default]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usageLimitPerTurn Context triple: [Fireblast, usageLimitPerTurn, Once by default]
-
A.
canBeUsedOncePer
chosen
Indicates that the associated action or resource is limited to a single use within each specified unit (such as per turn, per day, or per user).
-
B.
rateConstraint
Indicates a limitation or bound on the rate at which a process, transaction, or interaction is allowed to occur.
-
C.
attemptLimit
Indicates a restriction on how many times an action or operation may be attempted before it is stopped or blocked.
-
D.
renewalLimit
Indicates the maximum number of times an existing agreement, subscription, or permission can be renewed before it expires or must be re-established.
-
E.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.