Triple
T29458960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnesian Limestone Coast |
E747178
|
entity |
| Predicate | geologyFormedIn |
P33784
|
FINISHED |
| Object | Permian period |
—
|
NE NERFINISHED |
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: Permian period | Statement: [Magnesian Limestone Coast, geologyFormedIn, Permian period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologyFormedIn Context triple: [Magnesian Limestone Coast, geologyFormedIn, Permian period]
-
A.
geologicalFormationProcess
chosen
Indicates the natural geological process or set of processes by which a particular geological formation came into existence.
-
B.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
C.
geologyRelatedTo
Indicates a relationship where one geological entity, feature, or concept is connected, associated, or relevant to another within the domain of geology.
-
D.
stateOfFormation
Indicates the jurisdiction or region in which an entity was legally created or organized.
-
E.
hasCauseOfFormation
Indicates that one entity is the cause, origin, or formative factor leading to the creation or development of another entity.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 3:48 p.m.