Triple
T20765481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verbotene Stadt |
E511083
|
entity |
| Predicate | postReunificationStatus |
P130095
|
FINISHED |
| Object | former military area |
—
|
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: former military area | Statement: [Verbotene Stadt, postReunificationStatus, former military area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postReunificationStatus Context triple: [Verbotene Stadt, postReunificationStatus, former military area]
-
A.
reunificationStatus
Indicates the current state or outcome of efforts to bring previously separated entities back together into a single unified whole.
-
B.
postReunificationUse
chosen
Indicates how something is used or purposed after a reunification has taken place.
-
C.
postUnionStatus
Indicates that an entity publicly communicates or updates its status regarding unionization or union-related matters.
-
D.
statusInUnion
Indicates the specific role, standing, or membership condition an entity holds within a larger union or collective group.
-
E.
statusOfUnion
Indicates the current legal or formal state of a union or partnership between entities.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24bde0c8190b46986b89bf2e037 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:36 p.m.