Triple
T4765530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Part-Time Parliament |
E105799
|
entity |
| Predicate | originalDraftDate |
P32435
|
FINISHED |
| Object | late 1980s |
—
|
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: late 1980s | Statement: [The Part-Time Parliament, originalDraftDate, late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalDraftDate Context triple: [The Part-Time Parliament, originalDraftDate, late 1980s]
-
A.
createdAt
Indicates the date and time at which an entity was initially created or came into existence.
-
B.
issuedDocumentDate
chosen
Indicates the date on which a document was formally created, released, or made officially valid by the issuing party.
-
C.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
-
D.
originalCompletionDate
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
-
E.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.