Triple
T14229948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | neuroepithelial cyst |
E352725
|
entity |
| Predicate | hasLining |
P10266
|
FINISHED |
| Object | neuroepithelium |
—
|
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: neuroepithelium | Statement: [neuroepithelial cyst, hasLining, neuroepithelium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLining Context triple: [neuroepithelial cyst, hasLining, neuroepithelium]
-
A.
hasLiningMaterial
Indicates that one entity uses or contains another entity as the material forming its inner lining.
-
B.
mantlingLined
Indicates that the inner surface of a heraldic mantling is lined with a specified material, color, or pattern.
-
C.
isLinedWith
chosen
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
D.
hasLacing
Indicates a relationship where one entity is fastened, joined, or secured to another using laces or a lacing mechanism.
-
E.
hasDeFactoLine
Indicates that there exists an unofficial or non-legally recognized boundary or demarcation line functioning in practice between the related entities.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622b89fc8190af08dab9e1976759 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.