Triple
T4041641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gion district |
E83963
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Maruyama Park |
E322934
|
NE 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: Maruyama Park | Statement: [Gion district, near, Maruyama Park]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maruyama Park Context triple: [Gion district, near, Maruyama Park]
-
A.
Maruyama Park
chosen
Maruyama Park is a famous public park in Kyoto, Japan, especially known for its cherry blossoms and traditional atmosphere.
-
B.
Setagaya Park
Setagaya Park is a public green space in Tokyo’s Setagaya ward, known for its recreational facilities and local community use.
-
C.
Miyashita Park
Miyashita Park is a redeveloped urban park and shopping complex in Shibuya that combines green space, sports facilities, and commercial areas atop a multi-story building.
-
D.
Tsurumai Park
Tsurumai Park is a historic public park in Nagoya, Japan, known for its cherry blossoms, landscaped grounds, and cultural facilities.
-
E.
Yamashita Park
Yamashita Park is a famous seaside public park in Yokohama, Japan, known for its waterfront promenade, harbor views, and historic landmarks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb3a9314819095dcf47675eedb48 |
completed | March 9, 2026, 4:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b56b4d2cb081908dbca3bee5610cda |
completed | March 14, 2026, 2:06 p.m. |
Created at: March 9, 2026, 3:37 p.m.