Triple
T37007434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morciano di Romagna |
E915842
|
entity |
| Predicate | locatedInHinterland |
P52232
|
FINISHED |
| Object | Adriatic coast |
E156530
|
NE 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: Adriatic coast | Statement: [Morciano di Romagna, locatedInHinterland, Adriatic coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHinterland Context triple: [Morciano di Romagna, locatedInHinterland, Adriatic coast]
-
A.
locatedInland
Indicates that something is situated away from the coast or shoreline, within the interior of a land area.
-
B.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
-
C.
hasRuralHinterland
chosen
Indicates that a place or urban area is associated with and served by a surrounding rural region that supports it economically, socially, or functionally.
-
D.
isLocatedOnOutskirtsOf
Indicates that one entity is situated on the outer edge or peripheral area of another entity, rather than in its central or inner part.
-
E.
locatedInValleyOrPlain
Indicates that something is situated within a valley or on a plain.
- F. None of above.
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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e576cbc948190994ec2e9037ff01c |
completed | June 26, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.