Triple
T27612413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetResponse-PDU |
E700359
|
entity |
| Predicate | hasErrorStatusValue |
P82886
|
FINISHED |
| Object | tooBig |
—
|
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: tooBig | Statement: [GetResponse-PDU, hasErrorStatusValue, tooBig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasErrorStatusValue Context triple: [GetResponse-PDU, hasErrorStatusValue, tooBig]
-
A.
hasErrorType
Indicates that an entity is associated with, or classified by, a specific type or category of error.
-
B.
hasOutputStatus
Indicates that an entity is associated with a particular state or condition of its produced output.
-
C.
errorStatusSemantics
chosen
Indicates how the meaning or interpretation of an error status value should be understood within a given context or system.
-
D.
hasException
Indicates that a general rule, process, or condition does not apply in a particular case due to a specified exception.
-
E.
hasValidity
Indicates that something possesses a period or condition during which it is considered legally, logically, or functionally acceptable or in force.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:11 p.m.