Triple
T34667301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trichiuridae |
E890288
|
entity |
| Predicate | bodyMorphology |
P161608
|
FINISHED |
| Object | laterally compressed |
—
|
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: laterally compressed | Statement: [Trichiuridae, bodyMorphology, laterally compressed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyMorphology Context triple: [Trichiuridae, bodyMorphology, laterally compressed]
-
A.
limbMorphology
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
B.
bodyContour
Indicates the shape or outline of a body as defined by its external curves and boundaries.
-
C.
morphologicalTraits
chosen
Indicates a relationship where specific physical form or structural characteristics are attributed to or associated with an entity.
-
D.
bodyArt
Indicates that one entity has body art (such as tattoos, piercings, or similar modifications) applied to or present on another entity.
-
E.
bodyPartsGiveRiseTo
Indicates that certain body parts develop into, generate, or are the source of other anatomical structures or tissues.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722f81fc48190bed78b48e86e15e2 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.