Triple
T28038659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-body |
E708477
|
entity |
| Predicate | hasBodyTypeRelativeToAtlas |
P180415
|
FINISHED |
| Object | slimmer |
—
|
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: slimmer | Statement: [P-body, hasBodyTypeRelativeToAtlas, slimmer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyTypeRelativeToAtlas Context triple: [P-body, hasBodyTypeRelativeToAtlas, slimmer]
-
A.
belongsToBody
Indicates that something is a part of, or under the ownership/authority of, a particular body or organization.
-
B.
hasBodyName
Indicates that an entity has a specific name assigned to its physical body.
-
C.
hasBodyPlanType
Indicates that an organism possesses a particular overall structural or morphological body plan type.
-
D.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
-
E.
hasBodyPlanFeature
Indicates that an organism’s body plan includes a specific structural or morphological feature.
- F. None of above. chosen
Provenance (4 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 27, 2026, 8:23 p.m.