Triple
T14823991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pescorocchiano |
E348523
|
entity |
| Predicate | isHilltopSettlement |
P115964
|
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: [Pescorocchiano, isHilltopSettlement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHilltopSettlement Context triple: [Pescorocchiano, isHilltopSettlement, true]
-
A.
isOnHill
Indicates that one entity is located on or atop a hill relative to another reference frame or context.
-
B.
containsHill
Indicates that one entity geographically includes or encompasses a hill within its area or boundaries.
-
C.
hasHillDesignation
Indicates that an entity is assigned a specific designation or status related to a hill.
-
D.
hasHillTowns
Indicates that a place or region contains or is associated with one or more towns located on or around hills.
-
E.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe7a8dc8190bcb5ecfa1cbf1601 |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90806f3881908fcbfec5bd4ab4d2 |
completed | April 14, 2026, 7:07 p.m. |
Created at: April 10, 2026, 1:51 a.m.