Triple
T29728680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montravel |
E752257
|
entity |
| Predicate | locatedInBroadRegion |
P96807
|
FINISHED |
| Object | Nouvelle-Aquitaine |
—
|
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: Nouvelle-Aquitaine | Statement: [Montravel, locatedInBroadRegion, Nouvelle-Aquitaine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBroadRegion Context triple: [Montravel, locatedInBroadRegion, Nouvelle-Aquitaine]
-
A.
hasBroadRegion
Indicates that an entity is associated with, located in, or applicable to a relatively large or general geographic or conceptual region.
-
B.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
C.
locatedInTraditionalRegion
Indicates that an entity is situated within a specific traditional or historically recognized region.
-
D.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
E.
locatedInMetaregion
Indicates that one entity is geographically or administratively situated within a larger metaregion.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: April 28, 2026, 7:41 p.m.