Triple
T37061327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 宇治市 |
E917330
|
entity |
| Predicate | 姉妹都市国 |
P52852
|
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.
sisterCityCountry
chosen
Indicates that a city has an official sister-city relationship with a city located in the specified country.
-
B.
sisterMunicipalityWith
Indicates a formal partnership or twinning relationship between two municipalities, typically for cultural, social, or economic cooperation.
-
C.
hasSisterCityInspiration
Indicates that one city’s sister-city relationship serves as a model, influence, or source of inspiration for another city’s sister-city connection.
-
D.
hasSisterCityRelationshipType
Indicates a formal sister-city partnership relationship that exists between two municipalities or cities.
-
E.
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.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.