Triple
T30142885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D3 |
E766173
|
entity |
| Predicate | segmentCompetitors |
P164838
|
FINISHED |
| Object | BMW 7 Series |
—
|
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: BMW 7 Series | Statement: [D3, segmentCompetitors, BMW 7 Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: segmentCompetitors Context triple: [D3, segmentCompetitors, BMW 7 Series]
-
A.
underlyingCompanyMajorCompetitor
Indicates that one company serves as a primary or significant competitor to another company.
-
B.
peakMarketShare
Indicates the highest proportion of total market sales or customers that an entity has achieved over a specified period.
-
C.
competitorCategory
chosen
Indicates that two entities operate in the same competitive category or market segment, positioning them as rivals within that domain.
-
D.
competesWith
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
-
E.
sectorBenchmarkFor
Indicates that one entity serves as a benchmark or reference standard for evaluating performance within a particular sector or industry 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e8982648190b6bfb6b7f8b09d73 |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:18 p.m.