Triple
T32526160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Blue |
E831319
|
entity |
| Predicate | symptomProfile |
P129457
|
FINISHED |
| Object | severe respiratory illness |
—
|
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: severe respiratory illness | Statement: [Project Blue, symptomProfile, severe respiratory illness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symptomProfile Context triple: [Project Blue, symptomProfile, severe respiratory illness]
-
A.
viewsSymptoms
Indicates that one entity observes or examines the symptoms associated with another entity.
-
B.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
C.
symptom
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
D.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular disease.
-
E.
clinicalCondition
chosen
Indicates that one entity has, exhibits, or is associated with a particular medical or health-related condition described by the other 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c518439c81908002caf84440dd8a |
completed | May 3, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:01 a.m.