Triple
T184705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VOC |
E3954
|
entity |
| Predicate | reasonForDecline |
P6667
|
FINISHED |
| Object | corruption |
—
|
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: corruption | Statement: [VOC, reasonForDecline, corruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDecline Context triple: [VOC, reasonForDecline, corruption]
-
A.
declinedDuring
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
B.
reasonForReoffer
Indicates the reason or justification for presenting something again after it was previously offered.
-
C.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
D.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
E.
rejectedOrModifiedBy
Indicates that a proposal, request, or item was either not accepted as-is or was altered by a particular agent or authority.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2592867108190b5d316c055575449 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566fb08c81908faff2fde552105d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a257e763d081908c54ad57d8d3060d |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.