Triple
T1635876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LotusScript |
E35358
|
entity |
| Predicate | errorHandlingMechanism |
P25610
|
FINISHED |
| Object | On Error statement |
—
|
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: On Error statement | Statement: [LotusScript, errorHandlingMechanism, On Error statement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errorHandlingMechanism Context triple: [LotusScript, errorHandlingMechanism, On Error statement]
-
A.
errorHandlingModel
chosen
Indicates how a system or component manages, responds to, and recovers from errors or exceptional conditions during operation.
-
B.
errorRecovery
Indicates that an entity detects a failure or error condition and initiates actions to restore normal or acceptable operation.
-
C.
resolutionMechanism
Indicates the method, process, or system used to resolve a conflict, issue, or discrepancy between entities.
-
D.
exception
Indicates that a particular case does not follow the usual rule, pattern, or condition that applies to others.
-
E.
removalMechanism
Indicates the method or process by which something is removed, eliminated, or taken away from a system or 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.