Triple
T19772598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grail |
E474924
|
entity |
| Predicate | dataApproach |
P1717
|
FINISHED |
| Object | large-scale clinical data analysis |
—
|
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: large-scale clinical data analysis | Statement: [Grail, dataApproach, large-scale clinical data analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataApproach Context triple: [Grail, dataApproach, large-scale clinical data analysis]
-
A.
researchApproach
chosen
Indicates the methodological strategy or set of methods used to conduct and structure a research activity or investigation.
-
B.
dataAcquisition
Indicates the process by which one entity obtains, collects, or retrieves data from another source or system.
-
C.
dataProcessingStyle
Indicates the manner, method, or approach by which data is processed or handled in a given context.
-
D.
data
Indicates that one entity serves as informational content, measurements, or recorded values associated with another entity.
-
E.
formsApproachTo
Indicates that one entity develops or establishes a particular method, strategy, or way of dealing with or addressing another entity or situation.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535ce4d08190a1dfca2df95a8631 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.