Triple
T29179687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paratethys Sea |
E739711
|
entity |
| Predicate | temporalExtentDetail |
P105718
|
FINISHED |
| Object | Late Jurassic to Miocene |
—
|
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 Jurassic to Miocene | Statement: [Paratethys Sea, temporalExtentDetail, Late Jurassic to Miocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalExtentDetail Context triple: [Paratethys Sea, temporalExtentDetail, Late Jurassic to Miocene]
-
A.
hasTemporalEnd
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
B.
temporal scope
chosen
Indicates the time period or duration over which a particular relationship, condition, or fact holds true.
-
C.
hasTemporalResolution
Indicates that one entity specifies the level of temporal detail or granularity at which another entity’s data, observation, or process is measured or represented.
-
D.
hasTemporalUse
Indicates that something is used, applicable, or valid only during a specific time or temporal interval.
-
E.
temporalAspect
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 11:56 a.m.