Triple
T19773781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | respiratory syncytial virus |
E474952
|
entity |
| Predicate | routeOfEntry |
P52267
|
FINISHED |
| Object | nasal mucosa |
—
|
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: nasal mucosa | Statement: [respiratory syncytial virus, routeOfEntry, nasal mucosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeOfEntry Context triple: [respiratory syncytial virus, routeOfEntry, nasal mucosa]
-
A.
primaryPortalOfEntry
Indicates the main route or location through which something (such as a substance, pathogen, or agent) first enters a host or system.
-
B.
enteredCountryVia
Indicates that an entity came into a country using a specific entry point, route, or method.
-
C.
routeOfExposure
chosen
Indicates the pathway or method by which an agent, substance, or factor comes into contact with or enters an organism or system.
-
D.
servesAsMainPortOfEntryFor
Indicates that one location functions as the primary gateway or access point through which another entity typically enters a region or system.
-
E.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535e450c8190a2628245ae0d0bd3 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.