Triple
T37219821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aki Province |
E922845
|
entity |
| Predicate | hasImportantWaterBody |
P85029
|
FINISHED |
| Object | Seto Inland Sea |
—
|
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: Seto Inland Sea | Statement: [Aki Province, hasImportantWaterBody, Seto Inland Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportantWaterBody Context triple: [Aki Province, hasImportantWaterBody, Seto Inland Sea]
-
A.
hasBodyOfWaterType
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
-
B.
hasAreaWaterBody
Indicates that an entity includes, contains, or is associated with a body of water within its area or boundaries.
-
C.
hasAssociatedWaterBody
chosen
Indicates that one entity is linked to, or occurs in connection with, a specific body of water such as a river, lake, or sea.
-
D.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
E.
hasWatersOf
Indicates that a geographic or physical entity contains, is traversed by, or is otherwise characterized by specific bodies or types of water.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:15 p.m.