Triple
T34239487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | plans to ship Woody and the Roundup gang to Japan |
E878422
|
entity |
| Predicate | isIllegal |
P165164
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [plans to ship Woody and the Roundup gang to Japan, isIllegal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIllegal Context triple: [plans to ship Woody and the Roundup gang to Japan, isIllegal, true]
-
A.
isIllegalAction
chosen
Indicates that the referenced action violates laws or regulations and is therefore prohibited by legal authority.
-
B.
consideredIllegalUnder
Indicates that one entity is regarded as illegal or unlawful according to the laws, rules, or regulations defined by another entity.
-
C.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
D.
keptIllegally
Indicates that something is possessed, held, or maintained in violation of laws or regulations.
-
E.
wouldViolate
Indicates that performing the specified action or condition would break, infringe, or be inconsistent with a given rule, constraint, or obligation.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.