Triple
T3938579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasman Basin |
E90974
|
entity |
| Predicate | mainFormationPeriod |
P52657
|
FINISHED |
| Object | Late Cretaceous |
—
|
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: Late Cretaceous | Statement: [Tasman Basin, mainFormationPeriod, Late Cretaceous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainFormationPeriod Context triple: [Tasman Basin, mainFormationPeriod, Late Cretaceous]
-
A.
hasFormulationPeriod
Indicates the time span during which something is planned, designed, or developed before it is finalized or implemented.
-
B.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
-
C.
foundingPeriod
Indicates the time span or historical period during which an entity (such as an organization, settlement, or institution) was founded.
-
D.
historicalFormation
Indicates the process or circumstances through which something came into existence or took shape over time in history.
-
E.
containsFormation
Indicates that one entity spatially or structurally includes or encloses a formation as part of its extent or composition.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedcfd7d48190bbacee8b5b1b5070 |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeed3260cc8190bf294bdab507b1f9 |
completed | March 9, 2026, 3:54 p.m. |
Created at: March 9, 2026, 3:24 p.m.