Triple
T37704044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPA |
E939150
|
entity |
| Predicate | firstDemonstratedAt |
P1588
|
FINISHED |
| Object | University of Rochester |
E21319
|
NE 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: University of Rochester | Statement: [CPA, firstDemonstratedAt, University of Rochester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDemonstratedAt Context triple: [CPA, firstDemonstratedAt, University of Rochester]
-
A.
firstDemonstrated
chosen
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
-
B.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
C.
firstShowYear
Indicates the year in which something (such as a show, event, or work) was first presented or made publicly available.
-
D.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
E.
firstDeployedIn
Indicates the time or place where something (such as a system, product, or technology) was initially put into operational use or service.
- F. None of above.
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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40cdc9e86c81908c6474506c338fd8 |
completed | June 28, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.