Triple
T5963373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Prelude |
E132692
|
entity |
| Predicate | firstCompleteVersionDate |
P35832
|
FINISHED |
| Object | 1805 |
—
|
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: 1805 | Statement: [The Prelude, firstCompleteVersionDate, 1805]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCompleteVersionDate Context triple: [The Prelude, firstCompleteVersionDate, 1805]
-
A.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
B.
firstVersionYear
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
C.
firstReleaseVersion
Indicates the specific version identifier associated with the initial public release of something.
-
D.
earliestVersionDate
chosen
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
E.
firstFullVersionReference
Indicates that one entity serves as the initial complete or fully realized version to which another entity refers or is linked.
- 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_69c0086c2364819091e9fe2f58fa2517 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:03 p.m.