Triple
T26152678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tofane group |
E659869
|
entity |
| Predicate | popularAccessTown |
P167072
|
FINISHED |
| Object | Cortina d'Ampezzo |
—
|
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: Cortina d'Ampezzo | Statement: [Tofane group, popularAccessTown, Cortina d'Ampezzo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularAccessTown Context triple: [Tofane group, popularAccessTown, Cortina d'Ampezzo]
-
A.
popularTown
Indicates that a town is widely liked, frequently visited, or well-regarded by many people.
-
B.
accessTown
Indicates that an entity has the ability or permission to enter or make use of a particular town.
-
C.
countryOfAccessTown
Indicates the country in which the specified town providing access (e.g., to a service, resource, or location) is located.
-
D.
majorAccessTown
Indicates that a location serves as a primary or significant access point to a town, such as a main route, gateway, or connection hub.
-
E.
fromTown
Indicates that one entity originates from, or is associated as being from, a particular town represented by the other entity.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 26, 2026, 8:26 p.m.