Triple
T33453728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shingu, Fukuoka |
E856712
|
entity |
| Predicate | isCoastalResidentialAreaOf |
P176638
|
FINISHED |
| Object | Fukuoka City |
—
|
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: Fukuoka City | Statement: [Shingu, Fukuoka, isCoastalResidentialAreaOf, Fukuoka City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoastalResidentialAreaOf Context triple: [Shingu, Fukuoka, isCoastalResidentialAreaOf, Fukuoka City]
-
A.
isCoastalArea
Indicates that a given area is located along or directly adjacent to a sea or ocean coastline.
-
B.
isCoastalTo
Indicates that one place is located along or directly borders the coastline of another body of water or coastal region.
-
C.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
-
D.
isCoastalLocation
Indicates that a location is situated on or directly adjacent to a sea, ocean, or significant coastal body of water.
-
E.
isCoastalLocality
Indicates that a locality is situated on or directly adjacent to a sea, ocean, or significant coastal body of water.
- F. None of above. chosen
Provenance (4 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:37 a.m.