Triple
T25096118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 熊本市 |
E628592
|
entity |
| Predicate | 友好都市 |
P31399
|
FINISHED |
| Object | ハイデルベルク市（ドイツ連邦共和国） |
—
|
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: ハイデルベルク市（ドイツ連邦共和国） | Statement: [熊本市, 友好都市, ハイデルベルク市（ドイツ連邦共和国）]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 友好都市 Context triple: [熊本市, 友好都市, ハイデルベルク市（ドイツ連邦共和国）]
-
A.
friendshipCityOf
Indicates a relationship where a city is identified as the place associated with a friendship, such as where the friendship originated, is based, or is primarily maintained.
-
B.
sisterCityCountry
Indicates that a city has an official sister-city relationship with a city located in the specified country.
-
C.
sisterMunicipalityWith
chosen
Indicates a formal partnership or twinning relationship between two municipalities, typically for cultural, social, or economic cooperation.
-
D.
nearInternationalCity
Indicates that one entity is located geographically close to a city that has international significance, such as serving as a major global hub or capital.
-
E.
collaboratingCity
Indicates that two cities are working together in a cooperative or joint effort, such as on projects, initiatives, or shared goals.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b9651481908d4d7584717f5c59 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:25 a.m.