Triple
T27581506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA Technologies |
E699595
|
entity |
| Predicate | revenueYear |
P163293
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [CA Technologies, revenueYear, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revenueYear Context triple: [CA Technologies, revenueYear, 2018]
-
A.
revenueRightsTransferYear
Indicates the year in which the rights to receive revenue are transferred from one party to another.
-
B.
marketingYear
Indicates the specific 12‑month period used for planning, recording, or analyzing marketing or sales activities for a product or market.
-
C.
commissionYear
Indicates the year in which something (such as a work, project, or asset) was formally commissioned or authorized to be created or undertaken.
-
D.
revenue
Indicates the amount of income generated by an entity from its business activities or operations over a specified period.
-
E.
tradeYear
Indicates the specific calendar year in which a trade or commercial transaction took place or was recorded.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 2:02 p.m.