Triple
T15719626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bungo Channel |
E381054
|
entity |
| Predicate | isLocatedOnSideOf |
P86049
|
FINISHED |
| Object | east of Kyushu |
—
|
LITERAL 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: east of Kyushu | Statement: [Bungo Channel, isLocatedOnSideOf, east of Kyushu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedOnSideOf Context triple: [Bungo Channel, isLocatedOnSideOf, east of Kyushu]
-
A.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
B.
wasOnSideOf
Indicates that one entity supported, aligned with, or took the same side as another entity in a conflict, dispute, or opposing situation.
-
C.
onSide
chosen
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
D.
hasSummitOnSideOf
Indicates that the summit or highest point of one geographic feature is located on the side of another feature.
-
E.
locationSide
Indicates that one entity is positioned on a particular side (e.g., left, right, front, back) relative to another entity or reference point.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f932a248190b65ecfb2bc56e715 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.