Triple
T5114923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memantine |
E115307
|
entity |
| Predicate | wasFirstSynthesizedIn |
P61680
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Memantine, wasFirstSynthesizedIn, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstSynthesizedIn Context triple: [Memantine, wasFirstSynthesizedIn, 1968]
-
A.
firstSynthesisTarget
Indicates that an entity is the initial or primary target selected for synthesis in a process or workflow.
-
B.
firstProducedFor
Indicates that something was initially created, manufactured, or developed specifically for a particular recipient, purpose, or context.
-
C.
synthesizedAs
Indicates that one entity is produced or created in the form of another entity through a synthesis process.
-
D.
firstProducedAt
Indicates the location or context where something was originally created, manufactured, or brought into existence for the first time.
-
E.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ce6044819094166aebf0688665 |
completed | March 20, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:41 p.m.