Triple
T2491302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauternes |
E52047
|
entity |
| Predicate | supportsNobleRot |
P39769
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sauternes, supportsNobleRot, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNobleRot Context triple: [Sauternes, supportsNobleRot, yes]
-
A.
supportsPosition
Indicates that one entity endorses, upholds, or provides backing for the stance, viewpoint, or role represented by another entity.
-
B.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
C.
supportedMonarch
Indicates that one entity actively backed, endorsed, or maintained the rule or authority of a particular monarch.
-
D.
supportsValue
Indicates that one entity provides justification, evidence, or backing for the truth, relevance, or appropriateness of a particular value associated with another entity.
-
E.
supportsPrinciple
Indicates that one entity endorses, upholds, or actively backs a particular principle or doctrine.
- F. None of above. chosen
Provenance (4 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1914ca48190ab0a6cc5f1bd2f56 |
completed | March 7, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1318f7881908a8fc42943df4879 |
completed | March 7, 2026, 7:18 a.m. |
Created at: March 6, 2026, 9:45 p.m.