Triple
T17451035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neritimorpha |
E424912
|
entity |
| Predicate | shellFeature |
P127508
|
FINISHED |
| Object | thick shell |
—
|
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: thick shell | Statement: [Neritimorpha, shellFeature, thick shell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shellFeature Context triple: [Neritimorpha, shellFeature, thick shell]
-
A.
containerFeature
Indicates that one entity possesses or provides a specific feature, characteristic, or capability related to a container or containment context for another entity.
-
B.
scriptFeature
Indicates that a script includes, supports, or is characterized by a particular feature or capability.
-
C.
launcherFeature
Indicates that one entity functions as a feature, capability, or component provided by a launcher or launching system for another entity.
-
D.
bossFeature
Indicates that one entity serves as a primary or dominant feature, element, or component in relation to another.
-
E.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4513e57248190824b540865311f44 |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:47 a.m.