Triple
T17326237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Uji (1180) |
E420693
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Uji |
E120290
|
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: Uji | Statement: [Battle of Uji (1180), location, Uji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uji Context triple: [Battle of Uji (1180), location, Uji]
-
A.
Uji
chosen
Uji is a historic Japanese city near Kyoto renowned for its high-quality green tea and the UNESCO-listed Byōdō-in Temple.
-
B.
Ukaan
Ukaan is a little-documented Niger-Congo language spoken by a small community in southwestern Nigeria.
-
C.
Uzita
Uzita was a Native American chiefdom or village in present-day Florida that played a notable role in early Spanish exploration of the region.
-
D.
Uji Line
The Uji Line is a railway line in Japan operated by Keihan Electric Railway, connecting Kyoto’s city area with the historic Uji district known for its temples and tea culture.
-
E.
Ujitawara
Ujitawara is a rural town in Kyoto Prefecture, Japan, known for its tea production and scenic, mountainous landscapes.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d24e548190a766dd246a4d63d4 |
completed | April 19, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a018c4c2dc08190b60982abc9ac7c9c |
completed | May 11, 2026, 7:59 a.m. |
Created at: April 10, 2026, 5:43 a.m.