Triple
T31480125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shimabara Peninsula |
E803114
|
entity |
| Predicate | locatedInPrefectureCapitalDirection |
P203505
|
FINISHED |
| Object | east of Nagasaki City |
—
|
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: east of Nagasaki City | Statement: [Shimabara Peninsula, locatedInPrefectureCapitalDirection, east of Nagasaki City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPrefectureCapitalDirection Context triple: [Shimabara Peninsula, locatedInPrefectureCapitalDirection, east of Nagasaki City]
-
A.
prefectureCapitalNearby
Indicates that a prefecture’s capital city is geographically close to the referenced location.
-
B.
prefectureCapital
Indicates that a city serves as the administrative capital of a given prefecture.
-
C.
locatedInPrefectureCapitalRegion
Indicates that the subject is geographically situated within the capital region of a given prefecture.
-
D.
subprefectureCapital
Indicates that one entity serves as the administrative capital or seat of government for a given subprefecture.
-
E.
isInPrefecturalCapital
Indicates that one entity is located within the administrative boundaries of a prefectural capital city.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01926e2f348190a632eff5c91db5e0 |
completed | May 11, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_6a01923488f4819094d79a27f4bc8ab8 |
completed | May 11, 2026, 8:24 a.m. |
| PDg | Predicate description generation | batch_6a01926d10988190b6fbf03866337860 |
completed | May 11, 2026, 8:25 a.m. |
Created at: April 30, 2026, 9:31 p.m.