Triple
T24987098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL |
E625340
|
entity |
| Predicate | adminDistrictSeat |
P159058
|
FINISHED |
| Object | Seekirchen am Wallersee |
—
|
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: Seekirchen am Wallersee | Statement: [SL, adminDistrictSeat, Seekirchen am Wallersee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminDistrictSeat Context triple: [SL, adminDistrictSeat, Seekirchen am Wallersee]
-
A.
administrativeDistricts
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
-
B.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
C.
administrativeCouncilArea
Indicates that one entity is an administrative council area within which the other entity is located or governed.
-
D.
governmentalDistrictOf
Indicates that a governmental district is the administrative district to which a given entity belongs or in which it is located.
-
E.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 18, 2026, 6:03 a.m.