Triple
T3620784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | When Will Jesus Bring the Pork Chops? |
E76718
|
entity |
| Predicate | hasCoverFeature |
P50487
|
FINISHED |
| Object | image of George Carlin |
—
|
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: image of George Carlin | Statement: [When Will Jesus Bring the Pork Chops?, hasCoverFeature, image of George Carlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverFeature Context triple: [When Will Jesus Bring the Pork Chops?, hasCoverFeature, image of George Carlin]
-
A.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
B.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
C.
hasCoverName
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
-
D.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
E.
hasChartingCover
Indicates that one entity serves as the charting or graphical representation (cover) of another entity’s data or content.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2b9aa608190a680b250ecf63156 |
completed | March 8, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:23 p.m.