Triple
T30789579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FÜS |
E784054
|
entity |
| Predicate | registrationAuthorityLocation |
P162674
|
FINISHED |
| Object | Ostallgäu district office |
—
|
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: Ostallgäu district office | Statement: [FÜS, registrationAuthorityLocation, Ostallgäu district office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationAuthorityLocation Context triple: [FÜS, registrationAuthorityLocation, Ostallgäu district office]
-
A.
registrationAuthorityLocatedIn
chosen
Indicates that the authority responsible for registration is situated within a specified geographic or jurisdictional location.
-
B.
registrationAuthorityCountry
Indicates the country that serves as the official authority responsible for registering the entity.
-
C.
addressesAuthority
Indicates that one entity directs communication, requests, or appeals to another entity recognized as having authority or decision-making power.
-
D.
locationOfAwardingBody
Indicates the place or venue where the awarding body confers or grants an award.
-
E.
inscriptionLocation
Indicates the place or surface on which an inscription is written or engraved.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:41 p.m.