Triple
T13942247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SARS-CoV-2 |
E335284
|
entity |
| Predicate | BaltimoreClassification |
P25488
|
FINISHED |
| Object | Group IV |
—
|
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: Group IV | Statement: [SARS-CoV-2, BaltimoreClassification, Group IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BaltimoreClassification Context triple: [SARS-CoV-2, BaltimoreClassification, Group IV]
-
A.
BaltimoreConference
Indicates a conference event that takes place in or is associated with Baltimore.
-
B.
BaltimoreOwner
Indicates that an entity owns, possesses, or holds ownership rights over something specifically in the context of Baltimore.
-
C.
areClassifiedBy
chosen
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
E.
basisOfClassification
Indicates that one entity serves as the criterion or foundation used to classify or categorize 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e0f6f3c8190a64058b732b0ac52 |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.