Triple
T27247198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruchottes-Chambertin |
E687375
|
entity |
| Predicate | slopePosition |
P83773
|
FINISHED |
| Object | mid-slope |
—
|
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: mid-slope | Statement: [Ruchottes-Chambertin, slopePosition, mid-slope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slopePosition Context triple: [Ruchottes-Chambertin, slopePosition, mid-slope]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
slopeType
Indicates the classification of a slope based on its geometric or physical characteristics, such as steepness, shape, or orientation.
-
C.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
-
D.
isOnSlopeOf
chosen
Indicates that one entity is located on the inclined surface or side of another entity, typically a sloping terrain or structure.
-
E.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626b2ba8c819090a9eb67cf9cb701 |
completed | May 2, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:42 a.m.