Triple
T16104917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janusz Korczak |
E390713
|
entity |
| Predicate | refusedOffer |
P57242
|
FINISHED |
| Object | to escape deportation without the children |
—
|
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: to escape deportation without the children | Statement: [Janusz Korczak, refusedOffer, to escape deportation without the children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusedOffer Context triple: [Janusz Korczak, refusedOffer, to escape deportation without the children]
-
A.
turnedDownOffer
chosen
Indicates that one party rejected or declined an offer made by another party.
-
B.
cannotOffer
Indicates that one entity is unable or not permitted to provide, propose, or extend an offer to another entity.
-
C.
rejectedAdvancesOf
Indicates that one entity declined, refused, or did not accept the romantic or sexual advances made by another entity.
-
D.
refusedMarriageProposalFrom
Indicates that one entity declined or rejected a marriage proposal made by another entity.
-
E.
refusedAction
Indicates that an entity deliberately declined or did not agree to perform a specific action requested, expected, or 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6b91a48190a04648d4cad2c4b1 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.