Triple
T19569718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perelman Center for Advanced Medicine |
E489677
|
entity |
| Predicate | buildingCost |
P3154
|
FINISHED |
| Object | 302000000 USD |
—
|
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: 302000000 USD | Statement: [Perelman Center for Advanced Medicine, buildingCost, 302000000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingCost Context triple: [Perelman Center for Advanced Medicine, buildingCost, 302000000 USD]
-
A.
constructionCost
chosen
Indicates the monetary or resource expenditure required to build or construct something.
-
B.
economicCost
Indicates the financial burden, expense, or resource expenditure associated with an action, event, or relationship between entities.
-
C.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
D.
constructionCostCurrency
Indicates the currency in which the construction cost of something is expressed.
-
E.
programCost
Indicates the monetary or resource expenditure required to implement, run, or participate in a particular program.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f7a74e88190a58d5274050a7d32 |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.