Triple
T21603233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCV |
E533102
|
entity |
| Predicate | oftenConfiguredWith |
P4791
|
FINISHED |
| Object | sliding side doors |
—
|
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: sliding side doors | Statement: [LCV, oftenConfiguredWith, sliding side doors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenConfiguredWith Context triple: [LCV, oftenConfiguredWith, sliding side doors]
-
A.
oftenConfiguredAs
Indicates that one entity is frequently set up, arranged, or used in the form or role of another entity.
-
B.
usedWith
chosen
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
C.
partlyConfiguredAs
Indicates that one entity is only partially set up, arranged, or defined to function as another entity or in another role.
-
D.
configuredPer
Indicates that one entity is set up, arranged, or parameterized according to the specifications or requirements of another entity.
-
E.
oftenStatedWith
Indicates that one statement, fact, or expression is frequently mentioned or asserted together with another.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e31c80819090fdd63b5c103acb |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.