Triple
T6716146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Caprice |
E153271
|
entity |
| Predicate | policePackageCode |
P72838
|
FINISHED |
| Object | 9C1 |
—
|
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: 9C1 | Statement: [Chevrolet Caprice, policePackageCode, 9C1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policePackageCode Context triple: [Chevrolet Caprice, policePackageCode, 9C1]
-
A.
policeNumber
Indicates that an entity is associated with a specific police-related identification or reference number.
-
B.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
C.
policeBureau
Indicates that an entity functions as or is associated with a police bureau or police department.
-
D.
includedPoliceComponent
Indicates that one entity contains or incorporates a police-related component, unit, or element as part of its structure or composition.
-
E.
policeUnit
Indicates that one entity is a police unit (such as a department, squad, or division) associated with or responsible for another entity.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d125db3c8190aad28919226a16da |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d11fab808190b18160ff3829fcc6 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:07 p.m.