Triple
T23778402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Difference Engine No. 2 |
E587740
|
entity |
| Predicate | firstCompleteConstruction |
P1511
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Difference Engine No. 2, firstCompleteConstruction, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCompleteConstruction Context triple: [Difference Engine No. 2, firstCompleteConstruction, 1991]
-
A.
constructionCompleted
chosen
Indicates that a construction process or project has been fully finished and reached its completed state.
-
B.
constructionCompletedUnder
Indicates that the completion of a construction project occurred under the responsibility, authority, or supervision of a specified agent, organization, or governing body.
-
C.
hasEndConstruction
Indicates that an entity is associated with, or terminates in, a specific construction or structural element at its end.
-
D.
churchConstructionCompleted
Indicates that the process of building or constructing a church has been finished.
-
E.
startOfConstructionApprox
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c629f0c08190baccce71ebc72650 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.