Triple
T5514590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qi |
E144648
|
entity |
| Predicate | interoperabilityProgram |
P10634
|
FINISHED |
| Object | Qi certification program |
—
|
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: Qi certification program | Statement: [Qi, interoperabilityProgram, Qi certification program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interoperabilityProgram Context triple: [Qi, interoperabilityProgram, Qi certification program]
-
A.
interoperabilityWith
Indicates that one system, component, or standard can effectively exchange and use information or services with another.
-
B.
interoperabilityStandard
Indicates that there is a standard or specification enabling different systems, components, or technologies to work together and exchange information seamlessly.
-
C.
linkedProgram
Indicates that one program is associated or connected to another program in a meaningful or dependent way.
-
D.
establishedProgram
chosen
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
-
E.
hasJointProgramWith
Indicates that two entities collaborate to offer a shared or coordinated program, initiative, or course of study.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f5b4e988190b590b4157cf089c1 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.