Triple
T11698292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CB2 receptor |
E278052
|
entity |
| Predicate | hasLowExpressionIn |
P101312
|
FINISHED |
| Object | central nervous system |
—
|
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: central nervous system | Statement: [CB2 receptor, hasLowExpressionIn, central nervous system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowExpressionIn Context triple: [CB2 receptor, hasLowExpressionIn, central nervous system]
-
A.
hasLow
Indicates that an entity possesses a value, level, or amount of something that is below a defined or expected threshold.
-
B.
hasExpression
Indicates that an entity displays or possesses a particular facial or emotional expression.
-
C.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
-
D.
hasLowerFrequencyIn
Indicates that one entity occurs or appears less frequently within a specified context than another entity.
-
E.
hasLocalExpression
Indicates that something has a specific form, representation, or manifestation that is valid or defined only within a particular local context or region.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47df68c81908a91919a69b4880d |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d89546a8688190b51455b5e12caf91 |
completed | April 10, 2026, 6:14 a.m. |
Created at: April 8, 2026, 9:40 p.m.