Triple
T34900046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gräfenhainichen |
E1006556
|
entity |
| Predicate | stateKey |
P197575
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Gräfenhainichen, stateKey, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateKey Context triple: [Gräfenhainichen, stateKey, 15]
-
A.
keyStatus
Indicates the current state or condition of a key (e.g., whether it is active, valid, revoked, or expired) in relation to its use or authorization.
-
B.
keyNonStateActor
Indicates that the referenced entity plays a primary or influential role as a non-governmental actor in the relevant context or system.
-
C.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
keyOf
Indicates that one entity functions as the key (identifier or access token) associated with another entity.
-
E.
keyStateActor
Indicates that an entity functions as a primary or central actor within a given state, situation, or context.
- F. None of above. chosen
Provenance (4 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
| PDg | Predicate description generation | batch_69fe9b013ec481908f89beddb9c4cd4e |
completed | May 9, 2026, 2:25 a.m. |
Created at: May 3, 2026, 4 p.m.