Triple
T21660308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biomphalaria pfeifferi |
E534576
|
entity |
| Predicate | hasShellShape |
P7380
|
FINISHED |
| Object | planispiral |
—
|
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: planispiral | Statement: [Biomphalaria pfeifferi, hasShellShape, planispiral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShellShape Context triple: [Biomphalaria pfeifferi, hasShellShape, planispiral]
-
A.
hasShell
Indicates that an entity possesses or is covered by a shell as a physical protective structure.
-
B.
shellType
chosen
Indicates the type or classification of a shell associated with an entity (e.g., its form, structure, or category).
-
C.
hasDistinctiveShape
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
D.
hasHemShape
Indicates that an item possesses a specific form or contour of its hem or lower edge.
-
E.
hasBayShape
Indicates that an entity possesses or exhibits a particular geometric or physical shape characteristic of a bay.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c07bcb88190a9864672c20325ff |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.