Triple
T2568847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einigungsvertrag |
E57615
|
entity |
| Predicate | veröffentlichtAm |
P30105
|
FINISHED |
| Object | 28. September 1990 |
—
|
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: 28. September 1990 | Statement: [Einigungsvertrag, veröffentlichtAm, 28. September 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: veröffentlichtAm Context triple: [Einigungsvertrag, veröffentlichtAm, 28. September 1990]
-
A.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
B.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
C.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
D.
isPublished
Indicates that an item has been formally made available to the public through some publishing process.
-
E.
hasPublicationDate
chosen
Indicates that an entity is associated with the specific date on which it was published.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd380d6e081909c124e8a0b7feef3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.