Triple
T30312723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | chicken tempura (toriten) |
E770969
|
entity |
| Predicate | localSpecialtyOf |
P17971
|
FINISHED |
| Object | Ōita Prefecture |
—
|
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: Ōita Prefecture | Statement: [chicken tempura (toriten), localSpecialtyOf, Ōita Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localSpecialtyOf Context triple: [chicken tempura (toriten), localSpecialtyOf, Ōita Prefecture]
-
A.
hasSpecialtyFood
chosen
Indicates that an entity offers, serves, or is associated with a particular type of specialty food.
-
B.
cityFish
Indicates that the subject is a type of fish that inhabits or is commonly found in a particular city.
-
C.
localPeople
Indicates a relationship where people are associated with, reside in, or originate from a particular local area or community.
-
D.
specialMunicipality
Indicates that an entity is designated as a special municipality, typically having a distinct administrative or legal status compared to regular municipalities.
-
E.
houseSpecialty
Indicates that something is the featured or signature item offered by a particular place or provider.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 7:50 p.m.