Triple
T10609815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THCA |
E275976
|
entity |
| Predicate | occursAs |
P76856
|
FINISHED |
| Object | acidic form of THC |
—
|
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: acidic form of THC | Statement: [THCA, occursAs, acidic form of THC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursAs Context triple: [THCA, occursAs, acidic form of THC]
-
A.
occursFor
Indicates that an event, process, or condition takes place in relation to, or on behalf of, a particular entity or context.
-
B.
occursAt
Indicates that an event or action takes place at a specific time or location.
-
C.
arisesAs
chosen
Indicates that one entity comes into existence, develops, or emerges as a result, form, or manifestation of another entity or process.
-
D.
occursBelow
Indicates that one event or object takes place or is positioned at a lower level or beneath another in a spatial or hierarchical sense.
-
E.
arisesIn
Indicates that something originates, emerges, or comes into existence within a specified context, source, or location.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df59468881909b0c67d3f08c4b76 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:32 p.m.