Triple
T36599030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CD340 |
E902871
|
entity |
| Predicate | hasCDDesignation |
P185919
|
FINISHED |
| Object | CD340 |
—
|
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: CD340 | Statement: [CD340, hasCDDesignation, CD340]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCDDesignation Context triple: [CD340, hasCDDesignation, CD340]
-
A.
hasBDDesignation
Indicates that an entity has been assigned a specific BD (Business Development or similar domain-specific) designation or classification.
-
B.
hasIspDesignation
Indicates that an entity has been assigned a specific Internet Service Provider (ISP) designation or classification.
-
C.
hasUSFDADesignation
Indicates that an entity has been granted a specific formal designation or status by the U.S. Food and Drug Administration (FDA).
-
D.
hasCriticalDesignation
Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
-
E.
hasNISTDesignation
Indicates that an entity is assigned a specific designation or identifier defined by NIST (the National Institute of Standards and Technology).
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.