Triple
T30621315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hercynian basement |
E779450
|
entity |
| Predicate | terminologyVariant |
P4680
|
FINISHED |
| Object | Variscan basement |
—
|
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: Variscan basement | Statement: [Hercynian basement, terminologyVariant, Variscan basement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminologyVariant Context triple: [Hercynian basement, terminologyVariant, Variscan basement]
-
A.
denotesVariantOf
Indicates that one entity is a variant or alternative form of another, typically sharing core identity or function with some differences.
-
B.
isSometimesUsedAsVariantOf
Indicates that one entity is occasionally employed as an alternative or substitute form of another entity, but not as its primary or standard version.
-
C.
terminologyNote
Indicates that there is an explanatory note or comment clarifying the use, meaning, or nuances of a specific term in the relationship.
-
D.
isShortenedVariantOf
Indicates that one form of an expression is a shortened or abbreviated version of another, longer form.
-
E.
variant
chosen
Indicates that one entity is an alternative form, version, or variation 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 8:27 p.m.