Triple
T19992794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NMDA receptor |
E494104
|
entity |
| Predicate | coAgonistRequired |
P86851
|
FINISHED |
| Object | glycine |
—
|
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: glycine | Statement: [NMDA receptor, coAgonistRequired, glycine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coAgonistRequired Context triple: [NMDA receptor, coAgonistRequired, glycine]
-
A.
coxRequirement
Indicates that something is a necessary condition or prerequisite related to a COX (cyclooxygenase) process, function, or regulation.
-
B.
requiresParticipationOf
chosen
Indicates that one entity’s occurrence, validity, or completion depends on the active involvement or participation of another entity.
-
C.
requiresAgreementWith
Indicates that one entity’s action, decision, or validity is contingent upon obtaining consent or formal agreement from another specified entity.
-
D.
mustGrant
Indicates that one party is obligated to give or allow something (such as a right, permission, or resource) to another party.
-
E.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe10ffc81908c94168b0a8ea9c9 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:31 p.m.