Triple
T27720850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivarais |
E698948
|
entity |
| Predicate | notableNaturalSite |
P47568
|
FINISHED |
| Object | Ardèche Gorges (part) |
—
|
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: Ardèche Gorges (part) | Statement: [Vivarais, notableNaturalSite, Ardèche Gorges (part)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNaturalSite Context triple: [Vivarais, notableNaturalSite, Ardèche Gorges (part)]
-
A.
notablePark
Indicates that a park is notable or significant in some recognized way, such as historical, cultural, or recreational importance.
-
B.
naturalMonument
Indicates that something is designated as a natural monument, typically a protected natural feature of special scientific, cultural, or aesthetic significance.
-
C.
naturalAttractionOf
Indicates a relationship where one entity is a natural feature or site that draws interest, attention, or visitors from another entity.
-
D.
localNatureSite
chosen
Indicates that a location is designated as a natural site of local significance or interest.
-
E.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a001cc0ff588190bb7c8a6fd427d02b |
completed | May 10, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_6a001b3ea18c8190aeda7a32b2697490 |
completed | May 10, 2026, 5:44 a.m. |
Created at: April 27, 2026, 3:06 p.m.