Triple
T3613151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jersey Mike’s Subs |
E76535
|
entity |
| Predicate | typicalServiceStyle |
P5621
|
FINISHED |
| Object | counter service |
—
|
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: counter service | Statement: [Jersey Mike’s Subs, typicalServiceStyle, counter service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServiceStyle Context triple: [Jersey Mike’s Subs, typicalServiceStyle, counter service]
-
A.
serviceUniform
Indicates that one entity is wearing or associated with a standardized uniform used for official or professional service.
-
B.
typicalServiceRequirement
Indicates that a certain condition, resource, or specification is normally needed or expected for a service to be properly provided or operated.
-
C.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
D.
serviceClass
chosen
Indicates the classification or category of service associated with or provided by an entity in the relationship.
-
E.
uniformStyle
Indicates that the related entities share the same or a consistent style, pattern, or formatting.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2786f808190be4e42734a79d74e |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.