Triple
T31771037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DECsystem-20 |
E810937
|
entity |
| Predicate | vendorAbbreviation |
P63459
|
FINISHED |
| Object | DEC |
—
|
NE NERFINISHED |
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: DEC | Statement: [DECsystem-20, vendorAbbreviation, DEC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vendorAbbreviation Context triple: [DECsystem-20, vendorAbbreviation, DEC]
-
A.
manufacturerAbbreviation
chosen
Indicates that one entity is an abbreviated or shortened form of the manufacturer's name for another entity.
-
B.
brandAbbreviation
Indicates that one brand name is an abbreviation or shortened form of another brand name.
-
C.
manufacturerStatus
Indicates the current operational or business condition of a manufacturer in relation to the product or agreement in question.
-
D.
vendorFamily
Indicates that one entity belongs to, or is part of, the same vendor’s organizational family or group as another entity.
-
E.
vendorDesignation
Indicates that one entity assigns or recognizes a specific vendor status, label, or role for another entity within a business or procurement context.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaff7648190a488163179a28fc2 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:33 p.m.