Triple
T29794627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 豊郷町 |
E756511
|
entity |
| Predicate | 県内での知名度 |
P65126
|
FINISHED |
| Object | 『けいおん！』ファンの間で特に高い |
—
|
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: 『けいおん！』ファンの間で特に高い | Statement: [豊郷町, 県内での知名度, 『けいおん！』ファンの間で特に高い]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 県内での知名度 Context triple: [豊郷町, 県内での知名度, 『けいおん！』ファンの間で特に高い]
-
A.
knownIn
chosen
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
B.
isInTownKnownFor
Indicates that one entity is located in a town that is notable or distinguished for the other entity.
-
C.
heldInProvince
Indicates that an event or activity takes place within the boundaries of a specified province.
-
D.
lessPopularInRegion
Indicates that one entity is less popular than another within a specified geographic region.
-
E.
locatedInRegionOfPrefecture
Indicates that one entity is geographically situated within a specific region that belongs to or is administered as part of a given prefecture.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674e5cf0c81908f779723cf602daf |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:14 p.m.