Triple
T27912286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eutin principality |
E705961
|
entity |
| Predicate | presentFederalState |
P87219
|
FINISHED |
| Object | Schleswig-Holstein |
—
|
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: Schleswig-Holstein | Statement: [Eutin principality, presentFederalState, Schleswig-Holstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentFederalState Context triple: [Eutin principality, presentFederalState, Schleswig-Holstein]
-
A.
stateFederation
Indicates that a state is a member of, or participates in, a larger federal union or federation.
-
B.
provinceState
Indicates that one entity is a province or state that is administratively contained within or associated with another, typically larger, territorial entity.
-
C.
includesFederalState
Indicates that one entity encompasses or contains both federal-level and state-level components, jurisdictions, or elements.
-
D.
modernStateName
chosen
Indicates that an entity is identified by the name of the corresponding modern (current) state or country.
-
E.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 6:51 p.m.