Triple
T6430739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metaxas Regime |
E128170
|
entity |
| Predicate | methodOfEstablishment |
P5191
|
FINISHED |
| Object | royal decree |
—
|
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: royal decree | Statement: [Metaxas Regime, methodOfEstablishment, royal decree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfEstablishment Context triple: [Metaxas Regime, methodOfEstablishment, royal decree]
-
A.
foundingMethod
chosen
Indicates the way or process by which an entity (such as an organization, institution, or settlement) was originally established or created.
-
B.
eraOfEstablishment
Indicates the time period or historical era during which an entity was founded or established.
-
C.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
D.
governingBodyEstablished
Indicates that a particular governing body was formally created or brought into existence for an entity or domain.
-
E.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693b872c819082a7d0e257018831 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:44 p.m.