Triple
T25475114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grail |
E638409
|
entity |
| Predicate | systemOperationalStatus |
P5870
|
FINISHED |
| Object | still in use in some countries |
—
|
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: still in use in some countries | Statement: [Grail, systemOperationalStatus, still in use in some countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemOperationalStatus Context triple: [Grail, systemOperationalStatus, still in use in some countries]
-
A.
operatingStatus
chosen
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
B.
systemOperatesOn
Indicates that a system performs operations, actions, or processing directly on a specified target or resource.
-
C.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
D.
systemTypeOperated
Indicates that an entity operates, controls, or runs a particular type of system.
-
E.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 2:25 p.m.