Triple
T30992341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Miletto |
E789698
|
entity |
| Predicate | nearestMajorMassif |
P159429
|
FINISHED |
| Object | Matese |
—
|
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: Matese | Statement: [Monte Miletto, nearestMajorMassif, Matese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorMassif Context triple: [Monte Miletto, nearestMajorMassif, Matese]
-
A.
nearestMountainMassif
chosen
Indicates that one mountain massif is the closest in distance to a given reference location or entity compared to all other mountain massifs.
-
B.
neighboringMassif
Indicates that one massif is geographically adjacent to or directly bordering another massif.
-
C.
highestMassifAmong
Indicates that one massif has the greatest height or prominence among a specified set of massifs.
-
D.
nearbyMountainRegion
Indicates that one location is situated close to or within the surrounding area of a mountainous region.
-
E.
nearestMajorTrailPass
Indicates the relationship where a given location is associated with the closest significant trail crossing or pass along a major trail network.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 8:56 p.m.