Triple
T3413614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shikoku Mountains |
E71954
|
entity |
| Predicate | formsDivideBetween |
P17951
|
FINISHED |
| Object | Pacific Ocean side of Shikoku |
—
|
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: Pacific Ocean side of Shikoku | Statement: [Shikoku Mountains, formsDivideBetween, Pacific Ocean side of Shikoku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsDivideBetween Context triple: [Shikoku Mountains, formsDivideBetween, Pacific Ocean side of Shikoku]
-
A.
formsNaturalDivideBetween
chosen
Indicates that one entity serves as a natural boundary or separation between two other entities.
-
B.
formsDivisionWith
Indicates that one entity combines with another to create or constitute a division or subgroup within a larger organization or structure.
-
C.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
D.
panelDivision
Indicates a relationship where a larger panel or board is divided into smaller sections or segments.
-
E.
divisionRenamedFrom
Indicates that a division currently known by one name was previously known by another specified name.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb927e8d081908a5ab283da93beb2 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.