Triple
T30140104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japantown |
E766104
|
entity |
| Predicate | hasTypicalEvent |
P7008
|
FINISHED |
| Object | Japanese cultural festivals |
—
|
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: Japanese cultural festivals | Statement: [Japantown, hasTypicalEvent, Japanese cultural festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalEvent Context triple: [Japantown, hasTypicalEvent, Japanese cultural festivals]
-
A.
typicalEvent
chosen
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
B.
hasOccasionalEvent
Indicates that an event or activity occurs irregularly or infrequently in relation to a given entity or context.
-
C.
typicalEventDay
Indicates the day on which an event is normally or most commonly held or occurs.
-
D.
hadEvent
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
E.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 29, 2026, 7:17 p.m.