Triple
T28482843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caledonian foreland basins |
E720740
|
entity |
| Predicate | developedInFrontOf |
P176725
|
FINISHED |
| Object | Caledonian orogen |
—
|
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: Caledonian orogen | Statement: [Caledonian foreland basins, developedInFrontOf, Caledonian orogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedInFrontOf Context triple: [Caledonian foreland basins, developedInFrontOf, Caledonian orogen]
-
A.
developedWithin
Indicates that something was created, produced, or brought into existence inside a specified context, boundary, or time frame.
-
B.
wasDevelopedIn
Indicates that an entity (such as a product, technology, or work) came into existence or was created during a specific time period or at a particular place.
-
C.
developedBefore
Indicates that one entity was developed or created earlier in time than another entity.
-
D.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
E.
developedWith
Indicates that something was created, built, or produced using a specified tool, technology, method, or collaborator.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 28, 2026, 2:56 a.m.