Triple
T10989105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azerbaijani National Council |
E259708
|
entity |
| Predicate | governmentFormSupported |
P40139
|
FINISHED |
| Object | republic |
—
|
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: republic | Statement: [Azerbaijani National Council, governmentFormSupported, republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentFormSupported Context triple: [Azerbaijani National Council, governmentFormSupported, republic]
-
A.
governmentFormUnder
Indicates that one governmental form or system operates under the authority, framework, or jurisdiction of another governmental form.
-
B.
governmentFormDefined
chosen
Indicates that the specific form or structure of governance for an entity has been formally specified or classified.
-
C.
governmentFormCreated
Indicates that one entity established or instituted a particular form or system of government for another entity.
-
D.
supportsForm
Indicates that one entity provides compatibility or backing for a particular form, format, or type associated with another entity.
-
E.
governmentFormBefore
Indicates that one form of government existed prior to another form of government in a temporal sequence.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d787b6d0b48190aaf959e2609d34e5 |
completed | April 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.