Triple
T25475115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grail |
E638409
|
entity |
| Predicate | systemProliferationStatus |
P163684
|
FINISHED |
| Object | widely proliferated |
—
|
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: widely proliferated | Statement: [Grail, systemProliferationStatus, widely proliferated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemProliferationStatus Context triple: [Grail, systemProliferationStatus, widely proliferated]
-
A.
runtimeStatus
Indicates the current operational state or condition of an entity while it is running or executing.
-
B.
resourceStatus
Indicates the current condition or state of availability, usability, or operational readiness of a given resource.
-
C.
patternSystemStatus
Indicates the current operational or health state of a pattern-based system or mechanism.
-
D.
managementStatus
Indicates the current state or condition of how something is being managed, such as whether it is under active management, unmanaged, or managed in a particular way.
-
E.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638d029148190877c103f0eeaf147 |
completed | May 2, 2026, 5:48 p.m. |
Created at: April 21, 2026, 2:25 p.m.