Triple
T33054727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpes Cottiae |
E845816
|
entity |
| Predicate | modernSiteOf |
P88073
|
FINISHED |
| Object | Susa, Italy |
—
|
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: Susa, Italy | Statement: [Alpes Cottiae, modernSiteOf, Susa, Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSiteOf Context triple: [Alpes Cottiae, modernSiteOf, Susa, Italy]
-
A.
modernSiteCorrespondsTo
chosen
Indicates that a present-day site occupies, aligns with, or directly relates to the location or extent of another (typically historical or earlier) site.
-
B.
nearModernSite
Indicates that one entity is located in close physical proximity to a site or location from the modern era.
-
C.
modernSiteOfCapital
Indicates that the subject location is the present-day site where the capital of the object political entity is situated.
-
D.
modernArchaeologicalSite
Indicates that a location functions as an archaeological site characterized by modern-era remains, research, or excavation activities.
-
E.
modernSiteIdentifiedInCentury
Indicates that the modern site was first identified or recognized during the specified century.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 1, 2026, 1:25 a.m.