Triple
T29840421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inning, Austria |
E757775
|
entity |
| Predicate | twinTownRegion |
P919
|
FINISHED |
| Object | Bavaria |
—
|
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: Bavaria | Statement: [Inning, Austria, twinTownRegion, Bavaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: twinTownRegion Context triple: [Inning, Austria, twinTownRegion, Bavaria]
-
A.
twinTownInCountry
Indicates that a town’s twin or sister city relationship is specifically with a town located in the given country.
-
B.
hasTwinTown
chosen
Indicates that two towns or cities are officially paired in a twinning relationship, typically for cultural, social, or economic exchange.
-
C.
twinCity
Indicates that two cities are officially recognized as twin (or sister) cities, typically signifying a formal partnership for cultural, economic, or social exchange.
-
D.
regionOfTown
Indicates that one entity is a specific area or district that forms part of a town.
-
E.
isTwinCityRegion
Indicates that two cities or metropolitan areas are officially recognized as forming a twin-city region, typically due to close geographic proximity and integrated economic, social, or administrative ties.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67609bfcc81909df94d5e0a488c42 |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:39 p.m.