Triple
T6421958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Phantom I |
E127963
|
entity |
| Predicate | typicalBodyStyles |
P3595
|
FINISHED |
| Object | limousine |
—
|
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: limousine | Statement: [Rolls-Royce Phantom I, typicalBodyStyles, limousine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBodyStyles Context triple: [Rolls-Royce Phantom I, typicalBodyStyles, limousine]
-
A.
carBodyStyle
Indicates the specific body configuration or design style that characterizes a car (e.g., sedan, hatchback, SUV).
-
B.
typicalBodyType
chosen
Indicates that one entity is the usual or characteristic body type associated with another entity.
-
C.
offersBodyStyle
Indicates that an entity (such as a manufacturer or model line) makes a particular vehicle body style available as an option.
-
D.
thirdGenerationBodyStyle
Indicates that the subject has the body style corresponding to the third generation of a particular model or design series.
-
E.
associatedWithBodyStyles
Indicates a relationship where something (such as a product, model, or item) is linked or connected to one or more specific body styles.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06903f67c8190a1e5babeede4e183 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.