Triple
T3841521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clitellata |
E93459
|
entity |
| Predicate | segmentationType |
P2563
|
FINISHED |
| Object | metameric segmentation |
—
|
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: metameric segmentation | Statement: [Clitellata, segmentationType, metameric segmentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: segmentationType Context triple: [Clitellata, segmentationType, metameric segmentation]
-
A.
segmentation
Indicates dividing something into distinct parts or segments based on certain criteria or boundaries.
-
B.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
C.
notableSegmentType
Indicates that a particular segment or portion of something is classified as being of notable or special significance by its type.
-
D.
hasSegmentType
chosen
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
-
E.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb235088190b115623e54ea2ab1 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.