Triple
T24336717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caprice Police Patrol Vehicle |
E613400
|
entity |
| Predicate | notSoldTo |
P69175
|
FINISHED |
| Object | general public in the United States |
—
|
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: general public in the United States | Statement: [Caprice Police Patrol Vehicle, notSoldTo, general public in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notSoldTo Context triple: [Caprice Police Patrol Vehicle, notSoldTo, general public in the United States]
-
A.
notSoldIn
Indicates that a product or item is unavailable for purchase within a specified market, region, or sales channel.
-
B.
cannotBeSoldBy
Indicates that one entity is not permitted or not allowed to sell another entity.
-
C.
notAvailableFor
chosen
Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
-
D.
notListedOn
Indicates that an entity is absent from, or does not appear in, a specified list, registry, or catalog.
-
E.
soldDueTo
Indicates that one entity was sold as a consequence of, or motivated by, another specified factor, event, or condition.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293212a0881908da028e81d26247d |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:57 a.m.