Triple
T16493354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baker Initiative |
E400620
|
entity |
| Predicate | rejectedPolicy |
P86103
|
FINISHED |
| Object | large-scale debt write-offs |
—
|
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: large-scale debt write-offs | Statement: [Baker Initiative, rejectedPolicy, large-scale debt write-offs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectedPolicy Context triple: [Baker Initiative, rejectedPolicy, large-scale debt write-offs]
-
A.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
B.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
C.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
D.
rejectedPractice
Indicates that one party has refused to accept, endorse, or continue a particular practice, method, or behavior associated with another party.
-
E.
rejectedConcept
chosen
Indicates that one entity has refused to accept, approve, or adopt a particular concept proposed by another entity.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e3189c8819097e6ba62f24b1f6c |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:13 a.m.