Triple
T32366752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TENAYA |
E827013
|
entity |
| Predicate | registrationDatabase |
P27278
|
FINISHED |
| Object | ClinicalTrials.gov |
—
|
NE NERFINISHED |
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: ClinicalTrials.gov | Statement: [TENAYA, registrationDatabase, ClinicalTrials.gov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationDatabase Context triple: [TENAYA, registrationDatabase, ClinicalTrials.gov]
-
A.
registrationSystem
chosen
Indicates a system or process responsible for recording, managing, and maintaining registrations or enrollments for entities.
-
B.
registro
Indicates that an entity is recorded, registered, or entered into an official or systematic record.
-
C.
registrationExample
Indicates that an instance serves as an illustrative or sample case of a particular registration.
-
D.
register
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
-
E.
registrationModel
Indicates the model, schema, or structure used to define how registrations are represented, processed, or stored in the system.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be9e9e1881909c41e3189585cfd0 |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:50 a.m.