Triple
T25580686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Préverenges |
E641230
|
entity |
| Predicate | hasNeighbouringUrbanCenter |
P36605
|
FINISHED |
| Object | Lausanne |
—
|
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: Lausanne | Statement: [Préverenges, hasNeighbouringUrbanCenter, Lausanne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighbouringUrbanCenter Context triple: [Préverenges, hasNeighbouringUrbanCenter, Lausanne]
-
A.
nearbyUrbanCenter
chosen
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
B.
connectsToUrbanCenter
Indicates that one entity has a direct or functional linkage to an urban center, such as through infrastructure, services, or regular interaction.
-
C.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
D.
isNearCapitalCity
Indicates that an entity is located close to, or in the immediate vicinity of, a capital city.
-
E.
hasMunicipalitySeatNearby
Indicates that the municipality’s administrative seat is located in close proximity to the referenced place or entity.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 21, 2026, 4:12 p.m.