Triple
T36571523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeneXpert system |
E902133
|
entity |
| Predicate | supportsAssay |
P89458
|
FINISHED |
| Object | Xpert MTB/RIF assay |
E902134
|
NE 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: Xpert MTB/RIF assay | Statement: [GeneXpert system, supportsAssay, Xpert MTB/RIF assay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAssay Context triple: [GeneXpert system, supportsAssay, Xpert MTB/RIF assay]
-
A.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
B.
supportsExperiment
Indicates that one entity provides the necessary resources, conditions, or assistance for an experiment to be conducted or to function as intended.
-
C.
supportsTestType
chosen
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
-
D.
supportsInstrument
Indicates that one entity provides assistance, resources, or functionality that enables another entity (the instrument) to operate or be used effectively.
-
E.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
- F. None of above.
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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39f90e2bf88190ad0b92137c3f961c |
completed | June 23, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.