Triple
T36919523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tweedy's farm |
E913140
|
entity |
| Predicate | threatToHens |
P186653
|
FINISHED |
| Object | being turned into pies |
—
|
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: being turned into pies | Statement: [Tweedy's farm, threatToHens, being turned into pies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatToHens Context triple: [Tweedy's farm, threatToHens, being turned into pies]
-
A.
riskToChickens
chosen
Indicates a relationship where something poses a potential danger, harm, or adverse impact specifically to chickens.
-
B.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
C.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
D.
isGoodForBackyardFlocks
Indicates that something is suitable or beneficial for keeping and managing small-scale backyard poultry flocks.
-
E.
threatensToDestroy
Indicates that one entity has expressed an intention or warning that it will cause the complete ruin or elimination of another entity or object.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:13 p.m.