Triple
T25537265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murex brandaris |
E640077
|
entity |
| Predicate | shellCharacteristic |
P127508
|
FINISHED |
| Object | elongated 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: elongated shell | Statement: [Murex brandaris, shellCharacteristic, elongated shell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shellCharacteristic Context triple: [Murex brandaris, shellCharacteristic, elongated shell]
-
A.
spanCharacteristic
Indicates that one entity has a particular measurable or descriptive property that characterizes the extent, duration, or range of another entity or phenomenon.
-
B.
podCharacteristic
Indicates a characteristic, feature, or property that is attributed to a pod.
-
C.
characteristicDevice
Indicates that a device is a defining or typical instrument, tool, or equipment associated with a particular entity, context, or activity.
-
D.
codeCharacteristic
Indicates that one piece of code possesses a specific property, feature, or quality in relation to another referenced aspect.
-
E.
shellFeature
chosen
Indicates that one entity functions as a characteristic or structural feature of another entity’s shell.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8911fb08190a234a87eaeee9f53 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 3:23 p.m.