Triple
T28879112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伊良部大橋 |
E732362
|
entity |
| Predicate | 所在海域の特徴 |
P77269
|
FINISHED |
| Object | 透明度の高い海域の上に架かる |
—
|
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: 透明度の高い海域の上に架かる | Statement: [伊良部大橋, 所在海域の特徴, 透明度の高い海域の上に架かる]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 所在海域の特徴 Context triple: [伊良部大橋, 所在海域の特徴, 透明度の高い海域の上に架かる]
-
A.
hasMaritimeFeature
chosen
Indicates that one entity possesses, contains, or is characterized by a maritime-related feature such as a sea, coast, harbor, or other oceanic element.
-
B.
oceanographicFeature
Indicates that one entity is an oceanographic feature (such as a current, front, eddy, or water mass) associated with or characterizing another entity.
-
C.
seaType
Indicates the specific classification or category of a sea associated with an entity.
-
D.
hasNearbyMarineFeature
Indicates that one entity is located close to a marine geographic feature associated with the other entity.
-
E.
hasCoastalCharacteristic
Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a4d874c819094de2d585e1f5816 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:41 a.m.