Triple
T26145626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindustan Motors |
E659653
|
entity |
| Predicate | ambassadorBodyStyle |
P51843
|
FINISHED |
| Object | sedan |
—
|
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: sedan | Statement: [Hindustan Motors, ambassadorBodyStyle, sedan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambassadorBodyStyle Context triple: [Hindustan Motors, ambassadorBodyStyle, sedan]
-
A.
oreBodyStyle
Indicates the specific body style or physical form that an ore or mineral deposit exhibits.
-
B.
associatedWithBodyStyles
Indicates a relationship where something (such as a product, model, or item) is linked or connected to one or more specific body styles.
-
C.
offersBodyStyle
chosen
Indicates that an entity (such as a manufacturer or model line) makes a particular vehicle body style available as an option.
-
D.
winnerBodyStyle
Indicates that one entity is the body style (e.g., sedan, SUV) associated with the winning entry or outcome in a competition or selection.
-
E.
officeHolderStyle
Indicates the formal title, manner of address, or stylistic designation used for a person holding a particular office or position.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60be803c88190980a8aafa935a52b |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:22 p.m.