Triple
T6939730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Hellenic Republic |
E160641
|
entity |
| Predicate | restorationOfMonarchy |
P27221
|
FINISHED |
| Object | 1935 |
—
|
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: 1935 | Statement: [Second Hellenic Republic, restorationOfMonarchy, 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorationOfMonarchy Context triple: [Second Hellenic Republic, restorationOfMonarchy, 1935]
-
A.
restoredMonarchy
chosen
Indicates that an entity caused or participated in the re-establishment of a previously abolished or suspended monarchy.
-
B.
monarchy
Indicates a system of governance in which supreme authority is vested in a single ruler, typically a king or queen, whose position is usually hereditary.
-
C.
restoredToThrone
Indicates that an entity regains a previously held throne or royal position after having lost or been removed from it.
-
D.
monarchDeposed
Indicates that a monarch has been removed from power, typically against their will, by force, coercion, or formal deposition.
-
E.
firstMonarchAfterRestoration
Indicates the monarch who was the first to assume the throne following a period of restoration of the monarchy or regime.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.