Triple
T35291921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Vulture |
E1019249
|
entity |
| Predicate | isolatedMassif |
P182694
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Monte Vulture, isolatedMassif, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isolatedMassif Context triple: [Monte Vulture, isolatedMassif, true]
-
A.
hasMassif
Indicates that something possesses or is associated with a specific massif, typically a large, distinct section of a mountain range.
-
B.
neighboringMassif
Indicates that one massif is geographically adjacent to or directly bordering another massif.
-
C.
nearestMountainMassif
Indicates that one mountain massif is the closest in distance to a given reference location or entity compared to all other mountain massifs.
-
D.
highestMassifAmong
Indicates that one massif has the greatest height or prominence among a specified set of massifs.
-
E.
prominenceWithinMassif
Indicates the relative height or distinctness of a peak compared to the surrounding terrain within the same massif.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.