Triple
T7298303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocaine |
E167778
|
entity |
| Predicate | commonStreetForm |
P76075
|
FINISHED |
| Object | cocaine hydrochloride |
—
|
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: cocaine hydrochloride | Statement: [Cocaine, commonStreetForm, cocaine hydrochloride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonStreetForm Context triple: [Cocaine, commonStreetForm, cocaine hydrochloride]
-
A.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
B.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
-
C.
formsCommunityIn
Indicates that an entity comes together with others to establish or participate in a community within a particular context or location.
-
D.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
E.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8f83c881909e8eae85410f9659 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb2d4c0c8190b4cc6fdfdb7f4827 |
completed | March 27, 2026, 8:40 p.m. |
Created at: March 27, 2026, 3 p.m.