Triple
T13093533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Artery/Tunnel Project |
E310522
|
entity |
| Predicate | finalCost |
P108009
|
FINISHED |
| Object | over 14 billion US dollars |
—
|
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 14 billion US dollars | Statement: [Central Artery/Tunnel Project, finalCost, over 14 billion US dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalCost Context triple: [Central Artery/Tunnel Project, finalCost, over 14 billion US dollars]
-
A.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
B.
finalValue
Indicates the resulting or ultimate value obtained after all relevant operations, changes, or calculations have been completed.
-
C.
increasedCostFor
Indicates that one entity causes or experiences a rise in the cost associated with another entity or activity.
-
D.
programCost
Indicates the monetary or resource expenditure required to implement, run, or participate in a particular program.
-
E.
finalProduct
Indicates that one entity is the completed or end-result product derived from another entity or process.
- F. None of above. chosen
Provenance (4 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:03 p.m.