Triple
T26966697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RP |
E679190
|
entity |
| Predicate | errorOn |
P162495
|
FINISHED |
| Object | yes-instances only |
—
|
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: yes-instances only | Statement: [RP, errorOn, yes-instances only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errorOn Context triple: [RP, errorOn, yes-instances only]
-
A.
errorSide
Indicates the side, party, or component on which an error occurs or is attributed in a given context.
-
B.
errorType
Indicates the specific category or kind of error associated with an event, action, or entity.
-
C.
errorTerm
Indicates the specific discrepancy or residual value that quantifies the difference between an observed outcome and its predicted or true value in a model or calculation.
-
D.
errorPhase
Indicates the specific stage or phase in a process or workflow during which an error occurred.
-
E.
errorDirection
Indicates the direction or orientation in which an error or deviation occurs relative to a reference or expected value.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f625402d808190be8279d895d2b27f |
completed | May 2, 2026, 4:24 p.m. |
Created at: April 27, 2026, 6:36 a.m.