Triple
T4881977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman Constitution of 1876 |
E109347
|
entity |
| Predicate | parliamentFirstConvened |
P36237
|
FINISHED |
| Object | 1877 |
—
|
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: 1877 | Statement: [Ottoman Constitution of 1876, parliamentFirstConvened, 1877]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentFirstConvened Context triple: [Ottoman Constitution of 1876, parliamentFirstConvened, 1877]
-
A.
firstParliamentStart
chosen
Indicates the date or point in time when an entity’s first parliamentary term or session began.
-
B.
firstCongressDate
Indicates the calendar date on which the first congress or formal assembly associated with an entity took place.
-
C.
congressBeganOn
Indicates the calendar date on which a particular session or term of a congress officially started.
-
D.
firstConstitutedIn
Indicates the time or context in which an entity (such as an organization, body, or structure) was originally formed or formally established.
-
E.
establishedAsModernParliament
Indicates that an institution or body was formally constituted or recognized as a modern parliamentary legislature.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dde6fcc8190a5aa7587f85632bd |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.