Triple
T28858812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naegleria fowleri |
E728806
|
entity |
| Predicate | portalOfEntry |
P66789
|
FINISHED |
| Object | nasal cavity |
—
|
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 cavity | Statement: [Naegleria fowleri, portalOfEntry, nasal cavity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portalOfEntry Context triple: [Naegleria fowleri, portalOfEntry, nasal cavity]
-
A.
primaryPortalOfEntry
chosen
Indicates the main route or location through which something (such as a substance, pathogen, or agent) first enters a host or system.
-
B.
rarePortalOfEntry
Indicates that the relationship involves an unusually uncommon or infrequent route or site through which something enters or gains access.
-
C.
servesAsMainPortOfEntryFor
Indicates that one location functions as the primary gateway or access point through which another entity typically enters a region or system.
-
D.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
E.
borderPass
Indicates that one entity crosses or moves through the boundary separating two regions or jurisdictions.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a14eaa081908113d246dbaf86dd |
completed | May 2, 2026, 8:09 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:46 a.m.