Triple
T25069024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Dukes of Saxe-Weimar-Eisenach |
E627857
|
entity |
| Predicate | titleCreatedAt |
P46587
|
FINISHED |
| Object | Congress of Vienna |
—
|
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: Congress of Vienna | Statement: [Grand Dukes of Saxe-Weimar-Eisenach, titleCreatedAt, Congress of Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCreatedAt Context triple: [Grand Dukes of Saxe-Weimar-Eisenach, titleCreatedAt, Congress of Vienna]
-
A.
titleCreatedFrom
Indicates that a title is derived or generated from another source, such as an existing entity, text, or identifier.
-
B.
titleCreation
chosen
Indicates that an entity is responsible for creating, originating, or authoring the title associated with another entity.
-
C.
titleDate
Indicates the date associated with a title, such as when it was granted, recorded, or became effective.
-
D.
titleCreationType
Indicates the manner or process by which a title was generated, assigned, or established for an entity.
-
E.
titleCreatedForAncestor
Indicates that a title or honor was established specifically in recognition of, or to commemorate, an ancestor of the referenced person.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 18, 2026, 6:10 a.m.