Triple
T2674262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pernand-Vergelesses |
E56419
|
entity |
| Predicate | exposure |
P15885
|
FINISHED |
| Object | mainly east- and south-facing slopes |
—
|
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: mainly east- and south-facing slopes | Statement: [Pernand-Vergelesses, exposure, mainly east- and south-facing slopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposure Context triple: [Pernand-Vergelesses, exposure, mainly east- and south-facing slopes]
-
A.
exposureType
chosen
Indicates the specific manner or context in which one entity is exposed to another entity, condition, or influence.
-
B.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
C.
exposed
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
-
D.
notableExposure
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
-
E.
exposureTime
Indicates the duration for which a subject or object is exposed to a particular condition, influence, or medium.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9b228cc819097f045b4a51d8e7c |
completed | March 7, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.