Triple
T34665096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carbone |
E890229
|
entity |
| Predicate | michelinStar |
P151628
|
FINISHED |
| Object | 1 (New York, various years) |
—
|
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: 1 (New York, various years) | Statement: [Carbone, michelinStar, 1 (New York, various years)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: michelinStar Context triple: [Carbone, michelinStar, 1 (New York, various years)]
-
A.
hasMichelinStar
Indicates that a restaurant or dining establishment has been awarded at least one Michelin star for its culinary quality.
-
B.
hasMichelinStarCount
chosen
Indicates the number of Michelin stars that have been awarded to a given entity, typically a restaurant or chef.
-
C.
awardedThreeMichelinStarsSince
Indicates that an entity (typically a restaurant) has been granted three Michelin stars starting from a specified time and has held that top rating since then.
-
D.
secondMichelinStarYear
Indicates the year in which an entity (typically a restaurant or chef) was awarded its second Michelin star.
-
E.
firstMichelinStarYear
Indicates the year in which an entity (typically a restaurant or chef) received its first Michelin star.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722f574388190b75d8c00917bb6f5 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.