Triple
T18296058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL/R 5000 |
E438232
|
entity |
| Predicate | typicalBuyer |
P10804
|
FINISHED |
| Object | performance car enthusiasts |
—
|
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: performance car enthusiasts | Statement: [SL/R 5000, typicalBuyer, performance car enthusiasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBuyer Context triple: [SL/R 5000, typicalBuyer, performance car enthusiasts]
-
A.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
B.
buyer
Indicates a relationship where one entity purchases or acquires goods, services, or rights from another entity in exchange for payment or compensation.
-
C.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
D.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
E.
personType
Indicates that an entity is classified as a particular type or category of person.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017c0f04819095cd9d59afc37caa |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.