Triple
T8540675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliminator |
E202185
|
entity |
| Predicate | typicalBuyerInterest |
P25915
|
FINISHED |
| Object | performance 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 enthusiasts | Statement: [Eliminator, typicalBuyerInterest, performance enthusiasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBuyerInterest Context triple: [Eliminator, typicalBuyerInterest, performance enthusiasts]
-
A.
soldInterestIn
Indicates that one entity has transferred or disposed of its ownership stake or financial interest in another entity or asset to a different party.
-
B.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
C.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
D.
primaryInterest
Indicates that one entity is the main or most significant focus of attention, concern, or engagement for another entity.
-
E.
marketPreference
chosen
Indicates a relationship where one entity favors, targets, or prioritizes a particular market or market segment over others.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6dfb2bc8190a41e32eca3c824c2 |
completed | March 31, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.