Triple
T23409930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernst-Reuter-Platz |
E560037
|
entity |
| Predicate | namedForRoleOfErnstReuter |
P112540
|
FINISHED |
| Object | Governing Mayor of Berlin |
—
|
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: Governing Mayor of Berlin | Statement: [Ernst-Reuter-Platz, namedForRoleOfErnstReuter, Governing Mayor of Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForRoleOfErnstReuter Context triple: [Ernst-Reuter-Platz, namedForRoleOfErnstReuter, Governing Mayor of Berlin]
-
A.
allyOfRudolf
Indicates a relationship where one entity is an ally or supporter of Rudolf.
-
B.
KarlVonMüllerRole
Indicates that an entity holds or is assigned the role or position associated with Karl von Müller.
-
C.
namedEditorInChief
Indicates that one entity has been designated to serve in the role of editor-in-chief for another entity, such as a publication or organization.
-
D.
namedPersonNotableFor
chosen
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
-
E.
endOfTermAsGauleiterOfVienna
Indicates the point in time when an individual's tenure as Gauleiter of Vienna comes to an end.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a510b3848190ae42679ef0bcd424 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.