Triple
T24407656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morar Group |
E615355
|
entity |
| Predicate | isPartOfBasementTo |
P155814
|
FINISHED |
| Object | Caledonian foreland basin |
—
|
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: Caledonian foreland basin | Statement: [Morar Group, isPartOfBasementTo, Caledonian foreland basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfBasementTo Context triple: [Morar Group, isPartOfBasementTo, Caledonian foreland basin]
-
A.
hasBasement
Indicates that a building or structure includes a basement level as part of its physical layout.
-
B.
hasBasementFeature
Indicates that a property’s basement includes or is characterized by a specific feature or attribute.
-
C.
basementType
Indicates the type or classification of a building’s basement as defined in the relationship.
-
D.
hasBasementUse
Indicates that a building or structure’s basement is used for a specified purpose or function.
-
E.
numberOfBasementLevels
Indicates the total count of basement levels associated with a given structure or property.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2957e8d5c8190bfed93aa308eb523 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f2915233c48190a181c8c1924e892c |
completed | April 29, 2026, 11:16 p.m. |
Created at: April 18, 2026, 2:05 a.m.