Triple
T36599884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peyer’s patches |
E902888
|
entity |
| Predicate | foundInLayer |
P66393
|
FINISHED |
| Object | lamina propria |
—
|
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: lamina propria | Statement: [Peyer’s patches, foundInLayer, lamina propria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInLayer Context triple: [Peyer’s patches, foundInLayer, lamina propria]
-
A.
foundInCanopyLayer
Indicates that something is located within or occurs in the canopy layer of a forest or vegetation structure.
-
B.
foundInStructure
chosen
Indicates that an entity is located within, contained by, or structurally part of another entity or structure.
-
C.
layerOf
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
D.
foundInDimension
Indicates that one entity exists or occurs within a specific dimension associated with another entity.
-
E.
foundInVolume
Indicates that one entity is physically or logically contained within, or occurs in, a specific volume (such as a book volume, data volume, or bounded collection).
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.