Triple
T32239431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wackernheim |
E823565
|
entity |
| Predicate | hasStateCodeISO3166-2 |
P164530
|
FINISHED |
| Object | DE-RP |
—
|
LITERAL FINISHED |
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: DE-RP | Statement: [Wackernheim, hasStateCodeISO3166-2, DE-RP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateCodeISO3166-2 Context triple: [Wackernheim, hasStateCodeISO3166-2, DE-RP]
-
A.
stateSubdivisionCode
Indicates the standardized code that identifies a specific subdivision (such as a state, province, or region) within a larger country or territory.
-
B.
hasISO3166-2CodePrefix
Indicates that one entity’s ISO 3166-2 code begins with, or is prefixed by, the code of another entity.
-
C.
usesISO3166-2Code
chosen
Indicates that an entity employs or references a subdivision identifier defined by the ISO 3166-2 standard.
-
D.
hasStateOrDistrict
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
-
E.
USStateFIPSLocation
Indicates a locational relationship where a place or entity is situated within, or associated with, a U.S. state identified by its FIPS (Federal Information Processing Standards) code.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: May 1, 2026, 12:39 a.m.