Triple
T1621939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019–20 NBA season |
E35049
|
entity |
| Predicate | healthProtocols |
P18421
|
FINISHED |
| Object | daily COVID-19 testing in bubble |
—
|
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: daily COVID-19 testing in bubble | Statement: [2019–20 NBA season, healthProtocols, daily COVID-19 testing in bubble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthProtocols Context triple: [2019–20 NBA season, healthProtocols, daily COVID-19 testing in bubble]
-
A.
healthProxy
Indicates that one entity is authorized to make health-related or medical decisions on behalf of another entity.
-
B.
publicHealthResponse
chosen
Indicates actions and measures taken by authorities or organizations to prevent, control, or mitigate health threats within a population.
-
C.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
D.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
E.
treats
Indicates that one entity provides medical care or therapeutic intervention to another entity.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf4a0ef748190ae52b9656474c0ef |
completed | March 6, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69a907c731808190a1d998155041b3c1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.