Triple
T27715099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor pork roll |
E698794
|
entity |
| Predicate | typicalServingRegion |
P201375
|
FINISHED |
| Object | New Jersey |
—
|
NE NERFINISHED |
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: New Jersey | Statement: [Taylor pork roll, typicalServingRegion, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServingRegion Context triple: [Taylor pork roll, typicalServingRegion, New Jersey]
-
A.
typicalRegionType
Indicates that a region is of a characteristic or commonly occurring type for a given context or entity.
-
B.
isTypicallyServedIn
Indicates that something (such as a food or drink) is most commonly or customarily presented or contained within a particular type of vessel or container.
-
C.
typicalVenueRegion2
Indicates that a venue is commonly or characteristically located within a particular secondary geographic region.
-
D.
servesRegionAcrossFrom
Indicates that a service or entity operates in a region that is geographically located directly across from another specified region.
-
E.
serviceRegion
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
| PDg | Predicate description generation | batch_69ffef8003c081909ec2413b4ea08d43 |
completed | May 10, 2026, 2:37 a.m. |
Created at: April 27, 2026, 3:04 p.m.