Triple
T16564935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elector of Frankfurt (1810–1813) |
E402435
|
entity |
| Predicate | titleRevived |
P124075
|
FINISHED |
| Object | prince-elector |
—
|
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: prince-elector | Statement: [Elector of Frankfurt (1810–1813), titleRevived, prince-elector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleRevived Context triple: [Elector of Frankfurt (1810–1813), titleRevived, prince-elector]
-
A.
titleRestored
Indicates that a previously held title or designation has been reinstated to an entity after having been removed, lost, or suspended.
-
B.
retitledAs
Indicates that an entity has been given a new title or name, replacing or supplementing its original one.
-
C.
themeRevived
Indicates that an entity is brought back to life, restored, or reactivated as the central participant or focus of an event or action.
-
D.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
-
E.
revivedBy
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e357711ea481909468147375051bb4 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.