Triple
T10513071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourg-lès-Valence |
E247963
|
entity |
| Predicate | hasGeographicalPosition |
P80554
|
FINISHED |
| Object | north of Valence |
—
|
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: north of Valence | Statement: [Bourg-lès-Valence, hasGeographicalPosition, north of Valence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeographicalPosition Context triple: [Bourg-lès-Valence, hasGeographicalPosition, north of Valence]
-
A.
hasGeocode
Indicates that an entity is associated with a specific geographic coordinate or coded location reference.
-
B.
isGeographicalEntity
Indicates that something exists as a distinct geographic feature, area, or place within physical space.
-
C.
hasRegionalPosition
chosen
Indicates that one entity holds a specific role, status, or placement within a defined geographic or regional context relative to another entity.
-
D.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
E.
containsGeographicalReferences
Indicates that something includes mentions or information about specific geographical locations or features.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509ca214481909b3ed9265e7a6704 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:27 p.m.