Triple
T4115820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grotte des Demoiselles |
E90287
|
entity |
| Predicate | hasSpeleothems |
P54726
|
FINISHED |
| Object | columns |
—
|
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: columns | Statement: [Grotte des Demoiselles, hasSpeleothems, columns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeleothems Context triple: [Grotte des Demoiselles, hasSpeleothems, columns]
-
A.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
B.
hasStratigraphicFeature
Indicates a relationship in which a geological unit, site, or context contains, exhibits, or is associated with a particular stratigraphic feature (such as a layer, horizon, or boundary) within its stratigraphic sequence.
-
C.
cavesUsedFor
Indicates that certain caves are utilized for a particular purpose, activity, or function by an entity.
-
D.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
E.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af03d5cce88190ad53bc6cfe10b21e |
completed | March 9, 2026, 5:31 p.m. |
Created at: March 9, 2026, 3:41 p.m.