Triple
T2532451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porky Pig |
E56191
|
entity |
| Predicate | endLineUsage |
P39415
|
FINISHED |
| Object | often delivers closing line of cartoons |
—
|
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: often delivers closing line of cartoons | Statement: [Porky Pig, endLineUsage, often delivers closing line of cartoons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endLineUsage Context triple: [Porky Pig, endLineUsage, often delivers closing line of cartoons]
-
A.
lineUses
Indicates that a particular line (such as a route, service, or connection) makes use of or is implemented using a specified resource, infrastructure, or element.
-
B.
usesLineCode
Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
-
C.
usedTerminal
Indicates that an entity made use of or interacted with a particular terminal or endpoint device.
-
D.
line6Terminus
Indicates the station or location where transit line 6 ends its route or service.
-
E.
alsoUsedOnLine
Indicates that something used in one context, medium, or location is additionally used on a specific line (such as a route, circuit, or sequence).
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd279cf108190b03fb6e0265f39d9 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd18e72a88190bdcf12b326d42fad |
completed | March 7, 2026, 7:19 a.m. |
Created at: March 6, 2026, 9:47 p.m.