Triple
T38561073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francisella tularensis |
E928076
|
entity |
| Predicate | hostCellType |
P188943
|
FINISHED |
| Object | macrophages |
—
|
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: macrophages | Statement: [Francisella tularensis, hostCellType, macrophages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCellType Context triple: [Francisella tularensis, hostCellType, macrophages]
-
A.
hostCells
Indicates that one entity provides living cells that support, contain, or are used by another entity (such as a virus, parasite, or experimental system).
-
B.
hostType
Indicates the category or kind of host associated with or responsible for the related entity or activity.
-
C.
cellType
Indicates the classification relationship that specifies what type of cell an entity is or is associated with.
-
D.
hostsClassification
Indicates that an entity serves as the host or environment in which a particular classification or categorized item resides or is applied.
-
E.
hostCellTypeOfNotableSpecies
chosen
Indicates that one entity is the type of host cell in which the other entity, a notable species, typically resides or replicates.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.