Triple
T26966716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RP |
E679190
|
entity |
| Predicate | acceptanceErrorType |
P43799
|
FINISHED |
| Object | false negatives allowed |
—
|
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: false negatives allowed | Statement: [RP, acceptanceErrorType, false negatives allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptanceErrorType Context triple: [RP, acceptanceErrorType, false negatives allowed]
-
A.
errorType
chosen
Indicates the specific category or kind of error associated with an event, action, or entity.
-
B.
acceptanceCondition
Indicates the criteria or circumstances under which something is approved, agreed to, or deemed valid.
-
C.
typeOfFailure
Indicates the specific kind or category of failure that occurred in relation to an entity or process.
-
D.
hasAcceptance
Indicates that one entity has formally received, approved, or agreed to something offered, proposed, or requested by another entity.
-
E.
rejectionCondition
Indicates the condition or set of criteria under which something (such as a request, offer, or item) is deemed unacceptable and therefore refused or discarded.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621210b788190ab9e910cd635f366 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:36 a.m.