Triple
T31997705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont-de-Marsan |
E817037
|
entity |
| Predicate | nearbyGeographicalArea |
P141258
|
FINISHED |
| Object | Landes forest |
—
|
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: Landes forest | Statement: [Mont-de-Marsan, nearbyGeographicalArea, Landes forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyGeographicalArea Context triple: [Mont-de-Marsan, nearbyGeographicalArea, Landes forest]
-
A.
hasNearbyGeographicalArea
chosen
Indicates that one geographical area is located in close spatial proximity to another geographical area.
-
B.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
C.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
D.
hasNearbyCityArea
Indicates that one area is geographically close to or adjacent to a city area.
-
E.
nearbyTo
Indicates that one entity is located close in distance or position to another 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 1, 2026, 12:14 a.m.