Triple
T29254171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ume Matsuri |
E741650
|
entity |
| Predicate | heldAtSiteWithFeature |
P125325
|
FINISHED |
| Object | large plum grove |
—
|
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: large plum grove | Statement: [Ume Matsuri, heldAtSiteWithFeature, large plum grove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldAtSiteWithFeature Context triple: [Ume Matsuri, heldAtSiteWithFeature, large plum grove]
-
A.
heldAtLocation
Indicates that an entity is being kept or stored at a specific location.
-
B.
hasOnsiteFeature
chosen
Indicates that one entity possesses or includes a particular feature that is physically present at its location or premises.
-
C.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
D.
isKeySiteOf
Indicates that a location serves as an important or central place for a particular event, activity, process, or function.
-
E.
isOnSiteWith
Indicates that two or more entities are physically present at the same site or location at the same time.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664ac0f488190ba511fe5c68babfc |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:35 p.m.