Triple
T5952325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunebedden |
E132428
|
entity |
| Predicate | geologicalOriginOfStones |
P66958
|
FINISHED |
| Object | boulders transported by Ice Age glaciers |
—
|
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: boulders transported by Ice Age glaciers | Statement: [Hunebedden, geologicalOriginOfStones, boulders transported by Ice Age glaciers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalOriginOfStones Context triple: [Hunebedden, geologicalOriginOfStones, boulders transported by Ice Age glaciers]
-
A.
stateGemstone
Indicates a relationship where a state is officially associated with or designated a particular gemstone.
-
B.
stoneQuality
Indicates the quality or grade assigned to a stone in terms of its characteristics or condition.
-
C.
surfaceGeologyKnown
Indicates that the composition or characteristics of an entity’s surface geology have been determined or are known.
-
D.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
-
E.
geologicalRole
Indicates the functional or classificatory role an entity plays within geological processes, structures, or contexts.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03edf98b881908e9dbc03d3fd6218 |
completed | March 22, 2026, 7:11 p.m. |
Created at: March 22, 2026, 4:02 p.m.