Triple
T3802213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honda Civic |
E91713
|
entity |
| Predicate | bodyStyleAvailability |
P23419
|
FINISHED |
| Object | varies by market and generation |
—
|
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: varies by market and generation | Statement: [Honda Civic, bodyStyleAvailability, varies by market and generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyStyleAvailability Context triple: [Honda Civic, bodyStyleAvailability, varies by market and generation]
-
A.
bodyVariant
Indicates that one entity is an alternative physical form or version of another entity’s body.
-
B.
associatedWithBodyStyles
chosen
Indicates a relationship where something (such as a product, model, or item) is linked or connected to one or more specific body styles.
-
C.
stylingEnables
Indicates that one entity provides or activates styling capabilities or visual formatting for another entity.
-
D.
styleInFull
Indicates that something is presented, written, or expressed in its complete, unabbreviated, or fully detailed form.
-
E.
supportsBodyType
Indicates that one entity is compatible with, designed for, or can accommodate a specified body type.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.