Triple
T5419188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montecarotto |
E121205
|
entity |
| Predicate | isInGeographicalArea |
P39182
|
FINISHED |
| Object | hilly inland Marche |
—
|
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: hilly inland Marche | Statement: [Montecarotto, isInGeographicalArea, hilly inland Marche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInGeographicalArea Context triple: [Montecarotto, isInGeographicalArea, hilly inland Marche]
-
A.
isInArea
chosen
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
B.
isInGeopoliticalEntity
Indicates that one entity is located within, or is a part of, a specific geopolitical unit such as a country, state, or city.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
isFromRegion
Indicates that one entity originates from, is associated with, or belongs to a specified geographic region.
-
E.
geographicAreaOfSupport
Indicates the geographic region or area within which support, assistance, or services are provided or applicable.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87e7ae388190b26d16d42e717023 |
completed | March 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.