Triple
T9128620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dickinsonia |
E219025
|
entity |
| Predicate | anteriorPosteriorAxis |
P87252
|
FINISHED |
| Object | present (inferred) |
—
|
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: present (inferred) | Statement: [Dickinsonia, anteriorPosteriorAxis, present (inferred)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anteriorPosteriorAxis Context triple: [Dickinsonia, anteriorPosteriorAxis, present (inferred)]
-
A.
primaryAxisFormation
Indicates the process or relationship by which the main structural or organizational axis of a system, body, or object is established or developed.
-
B.
formsAxisOf
Indicates that one entity serves together with another as the central line or primary axis around which a structure, system, or configuration is organized.
-
C.
ridgeAxis
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
-
D.
transportAxis
Indicates a directional path or axis along which something is transported or moved from one location to another.
-
E.
northSouthAxis
Indicates a spatial or directional relationship aligned along the north–south axis between entities.
- 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.