Triple
T36599909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peyer’s patches |
E902888
|
entity |
| Predicate | developsPredominantly |
P86290
|
FINISHED |
| Object | in early life |
—
|
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: in early life | Statement: [Peyer’s patches, developsPredominantly, in early life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developsPredominantly Context triple: [Peyer’s patches, developsPredominantly, in early life]
-
A.
developsWhen
Indicates that one condition, feature, or state comes into existence or forms as a result of another condition, feature, or state.
-
B.
developsDuring
chosen
Indicates that one process, condition, or characteristic comes into existence or forms over the course of a specified time period, phase, or event.
-
C.
developsUntil
Indicates that a process, condition, or entity continues to develop or progress up to a specified point or limit in time or state.
-
D.
isDevelopmentOf
Indicates that one entity is the development, evolution, or more advanced form derived from another entity.
-
E.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
- 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_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 3, 2026, 4:11 p.m.