Triple
T26984464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Valentino in Abruzzo Citeriore |
E679694
|
entity |
| Predicate | isLocatedInFoothillsOf |
P138580
|
FINISHED |
| Object | Apennines |
—
|
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: Apennines | Statement: [San Valentino in Abruzzo Citeriore, isLocatedInFoothillsOf, Apennines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInFoothillsOf Context triple: [San Valentino in Abruzzo Citeriore, isLocatedInFoothillsOf, Apennines]
-
A.
hasFoothillsOn
chosen
Indicates that one geographic feature is situated at or along the lower slopes or foothills of another, typically larger, landform such as a mountain or mountain range.
-
B.
locatedInMountain
Indicates that something is situated within, on, or as part of a mountain.
-
C.
locatedOnEasternSlopeOf
Indicates that one entity is situated on the eastern slope or side of another geographic feature or elevation.
-
D.
locatedInMountainRangeRegion
Indicates that a place or geographic entity is situated within the area covered by a specific mountain range.
-
E.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 6:47 a.m.