Triple
T15242801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classified Ventures (stake) |
E364299
|
entity |
| Predicate | relatedToTransaction |
P37
|
FINISHED |
| Object | sale of Cars.com stake |
—
|
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: sale of Cars.com stake | Statement: [Classified Ventures (stake), relatedToTransaction, sale of Cars.com stake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToTransaction Context triple: [Classified Ventures (stake), relatedToTransaction, sale of Cars.com stake]
-
A.
associatedWithTransactionType
Indicates that something has a connection or linkage to a specific type or category of transaction.
-
B.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
associatedTransactionRegion
Indicates that a transaction is linked to or occurs within a particular geographic or regional context.
-
D.
relatedToClaimOf
Indicates a relationship where something is connected or pertinent to a specific claim or assertion.
-
E.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007dcc33081908545ea1a1d2c19fe |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.