Triple
T21855035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrysler E-Class |
E539601
|
entity |
| Predicate | marketPositionRelativeTo |
P1850
|
FINISHED |
| Object | positioned below Chrysler New Yorker |
—
|
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: positioned below Chrysler New Yorker | Statement: [Chrysler E-Class, marketPositionRelativeTo, positioned below Chrysler New Yorker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketPositionRelativeTo Context triple: [Chrysler E-Class, marketPositionRelativeTo, positioned below Chrysler New Yorker]
-
A.
marketPosition
chosen
Indicates the relative standing or rank an entity holds within a specific market compared to its competitors.
-
B.
hasRelativeStrengthPosition
Indicates a comparative relationship where one entity’s strength is evaluated or ranked relative to another entity or a reference set.
-
C.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
E.
performanceRelativeToMarket
Indicates how an entity’s performance compares to a relevant market benchmark over a given period.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0bd5ba9288190af962117124f6483 |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.