Triple
T14999558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike’s Way |
E374047
|
entity |
| Predicate | isDefaultStyleFor |
P64886
|
FINISHED |
| Object | many Jersey Mike’s sandwiches |
—
|
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: many Jersey Mike’s sandwiches | Statement: [Mike’s Way, isDefaultStyleFor, many Jersey Mike’s sandwiches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefaultStyleFor Context triple: [Mike’s Way, isDefaultStyleFor, many Jersey Mike’s sandwiches]
-
A.
isDefaultFor
chosen
Indicates that something serves as the standard or fallback option that is automatically applied or selected for a given entity or context unless another choice is explicitly specified.
-
B.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
C.
hasSystemStyle
Indicates that one entity is associated with, or characterized by, a particular system-defined style of another entity.
-
D.
usesAsStyleOf
Indicates that one entity adopts or applies another entity as a stylistic model, method, or manner of expression.
-
E.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded71a5618819083ae96a79735ef98 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.