Triple
T5932530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICH E6 Good Clinical Practice |
E131969
|
entity |
| Predicate | E6(R2)Adopted |
P66984
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [ICH E6 Good Clinical Practice, E6(R2)Adopted, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: E6(R2)Adopted Context triple: [ICH E6 Good Clinical Practice, E6(R2)Adopted, 2016]
-
A.
eraSystem
Indicates a temporal classification relationship where an entity is associated with a particular era or chronological system used to organize time.
-
B.
eraType
Indicates the classification of a time period or era according to its type or category.
-
C.
sixthGenerationEndYear
Indicates the year in which a sixth generation (e.g., of a product, lineage, or series) comes to an end.
-
D.
éA
Indicates a directed association or influence from one entity toward another, where the first entity acts upon, affects, or is related to the second in a specified manner.
-
E.
era
Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03f26f51881908cc253fe5775a1fc |
completed | March 22, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c03355caf08190b960563a1aed23f9 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03f23dd20819089dbf0de0d913602 |
completed | March 22, 2026, 7:12 p.m. |
Created at: March 22, 2026, 4 p.m.