Triple
T12712197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ado-Odo/Ota |
E303746
|
entity |
| Predicate | hasMajorTown |
P316
|
FINISHED |
| Object | Ota |
E323849
|
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: Ota | Statement: [Ado-Odo/Ota, hasMajorTown, Ota]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ota Context triple: [Ado-Odo/Ota, hasMajorTown, Ota]
-
A.
Ota
chosen
Ota is a historically significant Awori town in southwestern Nigeria that has grown into a major industrial and educational hub.
-
B.
Olta
Olta is a small town in the La Rioja Province of northwestern Argentina that serves as an administrative and service center for the surrounding rural region.
-
C.
Oza
"Oza" is a prominent poetic work by Russian poet Andrei Voznesensky, reflecting his innovative style and experimental approach to verse.
-
D.
Otta
Otta is a small Norwegian town known as a regional transport hub and gateway to popular mountain and national park areas.
-
E.
Ōtoku
Ōtoku was a Japanese era name (nengō) of the late 11th century, used during the reign of Emperor Shirakawa.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96208fa6481909d6fd43654752a2d |
completed | April 10, 2026, 8:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f684e43424819080659ab152caae52 |
completed | May 2, 2026, 11:12 p.m. |
Created at: April 9, 2026, 5:23 p.m.