Triple
T37037113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slagelse Parish |
E916672
|
entity |
| Predicate | usesCivilRegistrationSystemOf |
P182948
|
FINISHED |
| Object | Denmark |
—
|
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: Denmark | Statement: [Slagelse Parish, usesCivilRegistrationSystemOf, Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCivilRegistrationSystemOf Context triple: [Slagelse Parish, usesCivilRegistrationSystemOf, Denmark]
-
A.
civilRegistration
Indicates the official recording of a person’s vital life event (such as birth, marriage, or death) by a civil authority.
-
B.
civilRegistrationCodeOf
Indicates that one entity is the civil registration code assigned to identify another entity in official civil records.
-
C.
civilRegistrationCategory
Indicates the specific type or classification of a civil registration event or record associated with an entity.
-
D.
usesNationalIDSystem
chosen
Indicates that an entity relies on a country's official national identification system for identification, verification, or related processes.
-
E.
civilRegistrationPrefixExample
Indicates that there is an example of a standard prefix used in civil registration identifiers or records.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 4:14 p.m.