Triple
T20479139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elsinore Corona |
E502403
|
entity |
| Predicate | hasGeologicalCharacteristics |
P89872
|
FINISHED |
| Object | ridges |
—
|
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: ridges | Statement: [Elsinore Corona, hasGeologicalCharacteristics, ridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeologicalCharacteristics Context triple: [Elsinore Corona, hasGeologicalCharacteristics, ridges]
-
A.
hasGeologicalNature
chosen
Indicates that something possesses a specific geological character, composition, or formation type.
-
B.
hasGeologicalSignificance
Indicates that something possesses notable importance or relevance within a geological context, such as Earth’s structure, history, or processes.
-
C.
hasGeographyCharacteristic
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
D.
geologicalDiversity
Indicates the degree and variety of different geological features, materials, and structures present within a given area or context.
-
E.
hasMineralFeature
Indicates that one entity possesses, contains, or is characterized by a specific mineral-related feature or attribute.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b54c8188190a71e35fab8d194a6 |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.