Triple
T5003983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloître Saint-André-le-Bas |
E112440
|
entity |
| Predicate | locatedInTownWithFeature |
P46334
|
FINISHED |
| Object | Vienne Roman heritage |
—
|
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: Vienne Roman heritage | Statement: [Cloître Saint-André-le-Bas, locatedInTownWithFeature, Vienne Roman heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTownWithFeature Context triple: [Cloître Saint-André-le-Bas, locatedInTownWithFeature, Vienne Roman heritage]
-
A.
locatedInOrNearModernSettlement
Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
-
B.
hasNearbyTown
Indicates that one location has a town situated close to it in geographic proximity.
-
C.
locatedInResortTown
Indicates that something is situated within the boundaries of a town that is primarily known as a resort or vacation destination.
-
D.
locatedInHubOf
Indicates that one entity is situated within the central hub or core area associated with another entity.
-
E.
notableLocationFeature
chosen
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.