Triple
T37496683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moraxella |
E931845
|
entity |
| Predicate | preferredSite |
P65518
|
FINISHED |
| Object | upper respiratory tract |
—
|
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: upper respiratory tract | Statement: [Moraxella, preferredSite, upper respiratory tract]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredSite Context triple: [Moraxella, preferredSite, upper respiratory tract]
-
A.
selectedAsSiteFor
Indicates that one entity has been chosen or designated to serve as the location or venue for another entity or activity.
-
B.
patronizedSite
Indicates that an entity regularly visited, used, or supported a particular site or location.
-
C.
recommendedLocation
chosen
Indicates that one entity suggests or endorses another entity as a suitable or preferred place for a particular purpose or activity.
-
D.
secondarySite
Indicates that one entity serves as an additional or subordinate location associated with another primary site.
-
E.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.