Triple
T37069570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bingo Province |
E917537
|
entity |
| Predicate | hasMajorHistoricalCity |
P3786
|
FINISHED |
| Object | Onomichi |
—
|
NE NERFINISHED |
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: Onomichi | Statement: [Bingo Province, hasMajorHistoricalCity, Onomichi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorHistoricalCity Context triple: [Bingo Province, hasMajorHistoricalCity, Onomichi]
-
A.
hasHistoricCity
chosen
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
B.
isHistoricalCity
Indicates that a city has historical significance, typically due to its age, past events, or preserved heritage.
-
C.
capitalOrMajorCityHistorically
Indicates that a place has historically served as a capital or as a major, centrally important city for a political or cultural entity.
-
D.
hasMajorHistoricalCentersIn
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
-
E.
passesHistoricCity
Indicates that a route, path, or entity travels through or goes by a city recognized for its historical significance.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a036c1282748190a820562bcd9aa5d9 |
completed | May 12, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_6a036bb5ca0c8190bd50abc197960b41 |
completed | May 12, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:14 p.m.