Triple
T16427614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obando Church |
E398983
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Obando |
E398983
|
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: Obando | Statement: [Obando Church, locatedIn, Obando]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Obando Context triple: [Obando Church, locatedIn, Obando]
-
A.
Obando
chosen
Obando is a coastal municipality in the province of Bulacan, Philippines, known for its annual fertility dance festival held in honor of Catholic patron saints.
-
B.
Tobata
Tobata is a ward in the city of Kitakyushu, Japan, known historically as an independent city and an important industrial and port area in northern Kyushu.
-
C.
Osakasayama
Osakasayama is a suburban city in Osaka Prefecture, Japan, known for its residential character and proximity to the Osaka metropolitan area.
-
D.
Maishima
Maishima is a man-made island in Osaka, Japan, known for its sports facilities, event venues, and waterfront recreational areas.
-
E.
Kameyama
Kameyama is a city in Mie Prefecture, Japan, known historically as a post town on the Tōkaidō and for its preserved castle ruins and traditional streetscapes.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328fc223c8190bbed29907351a6f6 |
completed | April 18, 2026, 6:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0091872e648190b805aa4e41bcbb6d |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:09 a.m.