Triple
T2708681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harima-nada Sea |
E59804
|
entity |
| Predicate | isShelteredBy |
P957
|
FINISHED |
| Object | surrounding islands of the Seto Inland Sea |
—
|
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: surrounding islands of the Seto Inland Sea | Statement: [Harima-nada Sea, isShelteredBy, surrounding islands of the Seto Inland Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShelteredBy Context triple: [Harima-nada Sea, isShelteredBy, surrounding islands of the Seto Inland Sea]
-
A.
hasNearbySanctuary
Indicates that one entity has a sanctuary or place of refuge located close to it in space or distance.
-
B.
hasShelters
Indicates that one entity provides, contains, or is associated with one or more shelters for another entity or purpose.
-
C.
hadSanctuaryOf
Indicates that an entity possessed or hosted a sanctuary dedicated to another entity.
-
D.
protectedBy
chosen
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
hasProtectedArea
Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda7542548190bbf6c947145f7f63 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.