Triple
T29739182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MQPUT |
E752547
|
entity |
| Predicate | errorReportedBy |
P164529
|
FINISHED |
| Object | completion code |
—
|
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: completion code | Statement: [MQPUT, errorReportedBy, completion code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errorReportedBy Context triple: [MQPUT, errorReportedBy, completion code]
-
A.
errorReporting
chosen
Indicates that one entity reports, logs, or communicates errors or faults related to another entity or process.
-
B.
errorOn
Indicates that one entity experiences, produces, or is associated with an error in relation to another entity or context.
-
C.
errorType
Indicates the specific category or kind of error associated with an event, action, or entity.
-
D.
reportedFor
Indicates that one entity has formally notified an authority or system about another entity’s behavior, condition, or status, typically to trigger review or action.
-
E.
errorSide
Indicates the side, party, or component on which an error occurs or is attributed in 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 7:47 p.m.