Triple
T15575529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AutoNation |
E374358
|
entity |
| Predicate | hasKeyRevenueSource |
P13615
|
FINISHED |
| Object | vehicle sales |
—
|
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: vehicle sales | Statement: [AutoNation, hasKeyRevenueSource, vehicle sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyRevenueSource Context triple: [AutoNation, hasKeyRevenueSource, vehicle sales]
-
A.
hasRevenueUnit
Indicates that an entity’s revenue is measured, reported, or associated in terms of a specified unit (e.g., currency or measurement unit).
-
B.
revenueSources
chosen
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
C.
isCommissionSource
Indicates that one entity serves as the origin or basis from which another entity’s commission or referral fee is generated.
-
D.
hasRevenueSystem
Indicates that one entity possesses, uses, or is associated with a particular revenue-generating system or mechanism.
-
E.
majorRevenueSource
Indicates that one entity serves as the primary or dominant source of revenue for another entity.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e2140388190a8df7b835eaa72ce |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:10 a.m.