Triple
T29738314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA ACF2 |
E752529
|
entity |
| Predicate | formerlyOfferedBy |
P197556
|
FINISHED |
| Object | Computer Associates International |
—
|
NE NERFINISHED |
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: Computer Associates International | Statement: [CA ACF2, formerlyOfferedBy, Computer Associates International]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyOfferedBy Context triple: [CA ACF2, formerlyOfferedBy, Computer Associates International]
-
A.
formerlyListedOn
Indicates that an entity was previously listed on a particular exchange, registry, or listing platform but is no longer listed there.
-
B.
formerUser
Indicates that an entity was previously a user of another entity or system but is no longer one.
-
C.
previouslyLicensedAs
Indicates that an entity held a license under a different name or status at some earlier time.
-
D.
formerName
Indicates that an entity was previously known by a different name in the past.
-
E.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
| PDg | Predicate description generation | batch_69fe9b013ec481908f89beddb9c4cd4e |
completed | May 9, 2026, 2:25 a.m. |
Created at: April 28, 2026, 7:46 p.m.