Triple
T32208156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardmore Basin |
E822726
|
entity |
| Predicate | structuralComplexityCause |
P118263
|
FINISHED |
| Object | Paleozoic orogenies |
—
|
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: Paleozoic orogenies | Statement: [Ardmore Basin, structuralComplexityCause, Paleozoic orogenies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralComplexityCause Context triple: [Ardmore Basin, structuralComplexityCause, Paleozoic orogenies]
-
A.
leafComplexity
Indicates the degree of division or elaboration in a leaf’s structure, such as whether it is simple, lobed, or compound.
-
B.
controlsComplexityBy
chosen
Indicates that one entity manages, limits, or regulates the complexity of another entity, process, or system.
-
C.
hasReasoningComplexity
Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
-
D.
hasComplexity
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
E.
constructionCaused
Indicates that one construction activity, process, or project is the cause of another event, condition, or outcome.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb8fea508190b1e1b41b8fbded49 |
completed | May 3, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:37 a.m.