Triple
T307519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM System/360 |
E6334
|
entity |
| Predicate | estimatedDevelopmentCost |
P4259
|
FINISHED |
| Object | over 5 billion US dollars (1960s) |
—
|
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: over 5 billion US dollars (1960s) | Statement: [IBM System/360, estimatedDevelopmentCost, over 5 billion US dollars (1960s)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedDevelopmentCost Context triple: [IBM System/360, estimatedDevelopmentCost, over 5 billion US dollars (1960s)]
-
A.
estimatedCost
chosen
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
B.
constructionCost
Indicates the monetary or resource expenditure required to build or construct something.
-
C.
estimatedCostComment
Indicates a textual note or explanation associated with an estimated cost, such as rationale, assumptions, or additional details about that estimate.
-
D.
acquisitionCost
Indicates the monetary amount or value required to obtain or purchase an entity.
-
E.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea313be88190b4441f3ea41a99e2 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93f38308190b4b480c951f1a1c3 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.