Triple
T34330458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lütmarsen |
E880988
|
entity |
| Predicate | hasFederalStateCode |
P67526
|
FINISHED |
| Object | NW |
—
|
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: NW | Statement: [Lütmarsen, hasFederalStateCode, NW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFederalStateCode Context triple: [Lütmarsen, hasFederalStateCode, NW]
-
A.
federalStateCode
chosen
Indicates that an entity is associated with, governed by, or identified through a specific federal state code within a country’s administrative or legal system.
-
B.
includesFederalState
Indicates that one entity encompasses or contains both federal-level and state-level components, jurisdictions, or elements.
-
C.
hasStateOrDistrict
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
-
D.
stateFederationAffiliation
Indicates that a state is formally affiliated with, or a member of, a particular federation or federal entity.
-
E.
federalStatus
Indicates that an entity holds a particular legal or administrative status under federal (national) authority or jurisdiction.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 1:58 a.m.