Triple
T28217306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W7 series |
E711346
|
entity |
| Predicate | enteredTrialService |
P64478
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [W7 series, enteredTrialService, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredTrialService Context triple: [W7 series, enteredTrialService, 2014]
-
A.
trialOccurredIn
Indicates that a particular trial took place within a specified location, venue, or jurisdiction.
-
B.
trialServiceStart
chosen
Indicates the point in time when a trial service or trial period for a service begins.
-
C.
relatedTrial
Indicates that one trial is associated with another trial, typically through relevance, similarity, or shared context within a broader study or legal/experimental framework.
-
D.
clinicalTrialContext
Indicates that an entity or event occurs within, is associated with, or is characterized by the setting, design, or conduct of a clinical trial.
-
E.
coordinatesClinicalTrialsFor
Indicates that one entity organizes, manages, or oversees the planning and execution of clinical trials on behalf of another entity.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:44 p.m.