Triple
T25746792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cala Goloritzé |
E648365
|
entity |
| Predicate | hasNotableRockFormationType |
P1326
|
FINISHED |
| Object | limestone pinnacle |
—
|
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: limestone pinnacle | Statement: [Cala Goloritzé, hasNotableRockFormationType, limestone pinnacle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRockFormationType Context triple: [Cala Goloritzé, hasNotableRockFormationType, limestone pinnacle]
-
A.
notableRockFormation
Indicates that one entity is a rock formation that is especially remarkable, distinctive, or well-known in relation to the other entity.
-
B.
hasNearbyRockFormation
Indicates that one entity is located close to or adjacent to a rock formation.
-
C.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
D.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
E.
hasStateRockFormation
Indicates a relationship where a state is associated with or designated as having a particular rock formation.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 22, 2026, 3:52 a.m.