Triple
T31641240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakano Ward |
E807461
|
entity |
| Predicate | hasSubcultureHub |
P2605
|
FINISHED |
| Object | Nakano Broadway |
—
|
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: Nakano Broadway | Statement: [Nakano Ward, hasSubcultureHub, Nakano Broadway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubcultureHub Context triple: [Nakano Ward, hasSubcultureHub, Nakano Broadway]
-
A.
hasSubcultureStatus
Indicates that an entity holds a particular role, recognition, or standing within a specific subculture or subcultural context.
-
B.
hasCulturalCommunity
Indicates that an entity is associated with, belongs to, or is part of a specific cultural community.
-
C.
hasSubcommunityIn
chosen
Indicates that a larger community contains or encompasses a smaller, distinct subcommunity located within it.
-
D.
hasLocalCult
Indicates that an entity is associated with a cult or worship practice that is specific to a particular locality or region.
-
E.
hasSubcultureDebate
Indicates that there is an ongoing or notable debate, disagreement, or contested discourse within or about a particular subculture.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: April 30, 2026, 10:49 p.m.