Triple
T12303130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porco |
E293281
|
entity |
| Predicate | derivationReason |
P24494
|
FINISHED |
| Object | pig-related taunt from rival fans |
—
|
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: pig-related taunt from rival fans | Statement: [Porco, derivationReason, pig-related taunt from rival fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivationReason Context triple: [Porco, derivationReason, pig-related taunt from rival fans]
-
A.
statedReason
chosen
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
B.
originalReason
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
-
C.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
D.
regulationReason
Indicates the reason or justification for which a regulation is established, applied, or enforced in relation to an entity or activity.
-
E.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.