Triple
T37326260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hungry Tiger |
E926610
|
entity |
| Predicate | refusesToSatisfy |
P187981
|
FINISHED |
| Object | own cruel appetites |
—
|
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: own cruel appetites | Statement: [The Hungry Tiger, refusesToSatisfy, own cruel appetites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusesToSatisfy Context triple: [The Hungry Tiger, refusesToSatisfy, own cruel appetites]
-
A.
notSatisfiedBy
Indicates that a requirement, condition, or expectation is not fulfilled or met by the referenced entity.
-
B.
rejectedRequirement
Indicates that a proposed requirement has been evaluated and explicitly not accepted or approved.
-
C.
refusesHelpFrom
Indicates that one entity declines or rejects assistance offered by another entity.
-
D.
refusesToLeave
Indicates that an entity is unwilling to depart from a place, situation, or state despite expectation or pressure to do so.
-
E.
refusedToExplain
Indicates that an entity declined or failed to provide an explanation about something to another entity or audience.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.