Triple
T33390564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thysanophrys |
E855031
|
entity |
| Predicate | headMorphology |
P29366
|
FINISHED |
| Object | broad flattened head |
—
|
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: broad flattened head | Statement: [Thysanophrys, headMorphology, broad flattened head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headMorphology Context triple: [Thysanophrys, headMorphology, broad flattened head]
-
A.
headShape
chosen
Indicates the characteristic form or contour of an entity’s head.
-
B.
headRegion
Indicates that one entity is the head or primary governing region of another entity.
-
C.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
D.
headAppearance
Indicates how an entity’s head looks or is visually characterized, such as its shape, features, or notable attributes.
-
E.
headGivesRiseTo
Indicates that one entity (the head) is the source or origin from which another entity arises, develops, or is produced.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:35 a.m.