Triple
T14094769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 World Car Design of the Year |
E339224
|
entity |
| Predicate | eligibleProducts |
P112795
|
FINISHED |
| Object | production cars |
—
|
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: production cars | Statement: [2014 World Car Design of the Year, eligibleProducts, production cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleProducts Context triple: [2014 World Car Design of the Year, eligibleProducts, production cars]
-
A.
eligiblePurchasers
Indicates that certain entities are permitted or qualified to make a particular purchase under specified rules or conditions.
-
B.
usesProduct
Indicates that one entity makes use of, applies, or employs a particular product.
-
C.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
-
D.
offersProduct
Indicates that one entity makes a product available to another entity, typically for sale or use.
-
E.
hasProduct
Indicates that an entity possesses, offers, or is associated with a particular product.
- F. None of above. chosen
Provenance (4 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb7fb3c819083266dbe7e93aaff |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.