Triple

T9128686
Position Surface form Disambiguated ID Type / Status
Subject Spriggina E219027 entity
Predicate hasPosteriorRegion P87254 FINISHED
Object segmented trunk 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: segmented trunk | Statement: [Spriggina, hasPosteriorRegion, segmented trunk]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPosteriorRegion
Context triple: [Spriggina, hasPosteriorRegion, segmented trunk]
  • A. hasRegion
    Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
  • B. hasAntipodalRegion
    Indicates that one region is located at the antipodal position of another region on a sphere, such that each point in one region corresponds to a point directly opposite it in the other.
  • C. hasRegionalPosition
    Indicates that one entity holds a specific role, status, or placement within a defined geographic or regional context relative to another entity.
  • D. locatedAfter
    Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
  • E. hasBaseRegion
    Indicates that one entity is situated upon, supported by, or primarily associated with a specific underlying region or area.
  • 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_69ca83debfc0819095800583e97ab10f completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca8cc85b081908ee80db0e3b7df15 completed April 1, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69cc6601d77881908299d58db6e64937 completed April 1, 2026, 12:25 a.m.
PDg Predicate description generation batch_69cc6a3c78388190a7436acc0e44ff55 completed April 1, 2026, 12:43 a.m.
Created at: March 30, 2026, 7:18 p.m.