Triple
T23737658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Difference Engine No. 1 |
E586579
|
entity |
| Predicate | projectCostIssue |
P51366
|
FINISHED |
| Object | cost overruns |
—
|
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: cost overruns | Statement: [Difference Engine No. 1, projectCostIssue, cost overruns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectCostIssue Context triple: [Difference Engine No. 1, projectCostIssue, cost overruns]
-
A.
programCostIssue
chosen
Indicates that there is a problem, concern, or irregularity related to the cost of a program.
-
B.
projectCostContext
Indicates the contextual factors or conditions under which a project's cost is defined, calculated, or interpreted.
-
C.
programCost
Indicates the monetary or resource expenditure required to implement, run, or participate in a particular program.
-
D.
economicCost
Indicates the financial burden, expense, or resource expenditure associated with an action, event, or relationship between entities.
-
E.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad356c88190ae29ce403145ee73 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.