Triple
T16081854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurussia |
E390128
|
entity |
| Predicate | paleolatitudeRange |
P54605
|
FINISHED |
| Object | equatorial regions |
—
|
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: equatorial regions | Statement: [Laurussia, paleolatitudeRange, equatorial regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paleolatitudeRange Context triple: [Laurussia, paleolatitudeRange, equatorial regions]
-
A.
paleogeographicAffinity
chosen
Indicates a relationship where entities share or are associated with a particular ancient geographic region or configuration of the Earth's surface.
-
B.
regionLongitudeRange
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
C.
geologicalRange
Indicates the span of geological time during which an entity (such as a taxon or formation) is known to have existed or been present.
-
D.
isBestSeenFromLatitudes
Indicates that something is most optimally or clearly observable when viewed from specific geographic latitudes.
-
E.
notVisibleFromLatitudesNorthOf
Indicates that the subject cannot be seen or observed from any location situated at latitudes north of the specified reference latitude.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.