Triple
T13135260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apocrita |
E312065
|
entity |
| Predicate | bodyPlanFeature |
P48124
|
FINISHED |
| Object | three distinct body regions: head, mesosoma, metasoma |
—
|
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: three distinct body regions: head, mesosoma, metasoma | Statement: [Apocrita, bodyPlanFeature, three distinct body regions: head, mesosoma, metasoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyPlanFeature Context triple: [Apocrita, bodyPlanFeature, three distinct body regions: head, mesosoma, metasoma]
-
A.
bodyPlan
Indicates the overall structural organization and arrangement of an organism’s body, including the layout and relationship of its major parts.
-
B.
hasBodyPlanFeature
chosen
Indicates that an organism’s body plan includes a specific structural or morphological feature.
-
C.
featuresBuilding
Indicates that one entity includes or incorporates a building as a notable component or characteristic.
-
D.
homeFeature
Indicates that a home possesses or includes a particular feature or amenity.
-
E.
floorPlanType
Indicates the specific layout or configuration category that a floor plan belongs to (e.g., studio, 1-bedroom, open-plan).
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b3d72c8190b69ae56435a954fa |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:08 p.m.