Triple
T3382166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virchow–Robin spaces |
E71210
|
entity |
| Predicate | filledWith |
P13702
|
FINISHED |
| Object | cerebrospinal fluid-like fluid |
—
|
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: cerebrospinal fluid-like fluid | Statement: [Virchow–Robin spaces, filledWith, cerebrospinal fluid-like fluid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filledWith Context triple: [Virchow–Robin spaces, filledWith, cerebrospinal fluid-like fluid]
-
A.
isTypicallyFilledWith
chosen
Indicates that one entity is commonly or usually occupied, loaded, or contained by another entity.
-
B.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
C.
emptiesInto
Indicates that one entity serves as the destination or outlet into which another entity flows, discharges, or is emptied.
-
D.
fueledBy
Indicates that one entity provides the energy or power source that enables the operation or functioning of another entity.
-
E.
frozenIn
Indicates that one entity is immobilized or preserved in a solid, frozen state within or by another entity.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5e9af608190bfb228ef99a87bb7 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.