Triple
T29034984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paleo-Tethys Ocean |
E737832
|
entity |
| Predicate | geologicTimeDisappearance |
P7427
|
FINISHED |
| Object | early Jurassic |
—
|
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: early Jurassic | Statement: [Paleo-Tethys Ocean, geologicTimeDisappearance, early Jurassic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicTimeDisappearance Context triple: [Paleo-Tethys Ocean, geologicTimeDisappearance, early Jurassic]
-
A.
extinctionPeriod
chosen
Indicates the time span during which an entity ceases to exist or is considered extinct.
-
B.
extinctionDate
Indicates the date or time at which an entity (typically a species or lineage) ceased to exist.
-
C.
extinctionEvent
Indicates a large-scale occurrence that causes the widespread or complete disappearance of one or more species or higher taxonomic groups.
-
D.
brokeUpDuringGeologicEra
Indicates that a previously unified landmass or geological entity separated into distinct parts during a specified geologic era.
-
E.
massExtinctionCount
Indicates the number of mass extinction events associated with or affecting a given entity or context.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 9:57 a.m.