Triple
T33953449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zürich |
E870500
|
entity |
| Predicate | formedReformationAllianceWith |
P201329
|
FINISHED |
| Object | Bern |
—
|
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: Bern | Statement: [Zürich, formedReformationAllianceWith, Bern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedReformationAllianceWith Context triple: [Zürich, formedReformationAllianceWith, Bern]
-
A.
laterReformedAs
Indicates that an entity was subsequently reorganized, renamed, or transformed into another entity at a later time.
-
B.
furtherReformedBy
Indicates that an existing reform, change, or modification to something is subsequently revised, extended, or improved by another agent or process.
-
C.
reformedOn
Indicates that an entity underwent a reform, change, or restructuring at a specific point in time or on a particular date.
-
D.
reformedBody
Indicates that an entity has undergone a process of structural or organizational change resulting in a newly formed or reorganized body.
-
E.
reformationMethod
Indicates the method or process by which something is reformed, corrected, or transformed from a prior state.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69ffebbcef80819099714fa9b7fda762 |
completed | May 10, 2026, 2:21 a.m. |
Created at: May 1, 2026, 1:49 a.m.