Triple
T36599911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peyer’s patches |
E902888
|
entity |
| Predicate | moreNumerousIn |
P72600
|
FINISHED |
| Object | children |
—
|
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: children | Statement: [Peyer’s patches, moreNumerousIn, children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moreNumerousIn Context triple: [Peyer’s patches, moreNumerousIn, children]
-
A.
manyMembersAre
Indicates that a large number of members within a group possess a specified property or participate in a particular role or condition.
-
B.
moreCommonAs
chosen
Indicates that one thing occurs or is observed more frequently in a specified role, form, or context than in another.
-
C.
moreExpressiveThan
Indicates that one entity conveys ideas, emotions, or information with greater richness, nuance, or clarity than another.
-
D.
heldMany
Indicates that one entity has possessed or maintained control over a large number or quantity of another entity over time.
-
E.
hasPlurality
Indicates that an entity or concept exists or is expressed in a plural form rather than a singular one.
- 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_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.