Triple
T37548252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madonie Regional Natural Park |
E933520
|
entity |
| Predicate | hasMountainPeak |
P10602
|
FINISHED |
| Object | Pizzo Carbonara |
—
|
NE NERFINISHED |
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: Pizzo Carbonara | Statement: [Madonie Regional Natural Park, hasMountainPeak, Pizzo Carbonara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMountainPeak Context triple: [Madonie Regional Natural Park, hasMountainPeak, Pizzo Carbonara]
-
A.
hasMountain
chosen
Indicates that a location or region possesses or contains at least one mountain.
-
B.
hasMountainRange
Indicates that one entity possesses, contains, or is geographically associated with a specific mountain range.
-
C.
hasMainMountain
Indicates that an entity is primarily associated with or characterized by a specific mountain as its main or most significant mountain.
-
D.
hasMainPeakElevation_m
Indicates the relationship that specifies the elevation, in meters, of the main or highest peak associated with an entity.
-
E.
hasHighestPeakHeight
Indicates that the subject entity possesses the greatest peak height compared to all other relevant entities in the given context.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:17 p.m.