Triple
T23102461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornalin |
E576068
|
entity |
| Predicate | originStatus |
P62853
|
FINISHED |
| Object | traditional Swiss variety |
—
|
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: traditional Swiss variety | Statement: [Cornalin, originStatus, traditional Swiss variety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originStatus Context triple: [Cornalin, originStatus, traditional Swiss variety]
-
A.
originalLocationStatus
chosen
Indicates the status or condition of an entity’s original location, such as whether it remains, has changed, or is otherwise affected.
-
B.
sourceStatus
Indicates the current state or condition of a given source within a process, system, or workflow.
-
C.
primaryOriginState
Indicates the state that serves as the main or original source location associated with an entity.
-
D.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
E.
originUse
Indicates that one entity is used as the original source, basis, or starting point for the creation, derivation, or use of 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de9fa8c81909fd26ff37173b85b |
completed | April 29, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.