Triple
T36600135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bursa of Fabricius |
E902893
|
entity |
| Predicate | epitheliumType |
P185923
|
FINISHED |
| Object | pseudostratified columnar epithelium |
—
|
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: pseudostratified columnar epithelium | Statement: [bursa of Fabricius, epitheliumType, pseudostratified columnar epithelium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epitheliumType Context triple: [bursa of Fabricius, epitheliumType, pseudostratified columnar epithelium]
-
A.
cellType
Indicates the classification relationship that specifies what type of cell an entity is or is associated with.
-
B.
cellTypeUsed
Indicates that a particular type of cell is employed or utilized in relation to another entity or process.
-
C.
polypType
Indicates the specific morphological or histological classification assigned to a polyp.
-
D.
biologicType
Indicates the specific biological category or class to which an entity (such as a substance, agent, or product) belongs.
-
E.
cellInteractionType
Indicates the specific kind of interaction or relationship occurring between cells, such as communication, adhesion, or signaling.
- F. None of above. chosen
Provenance (4 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.