Triple
T34626039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaunoir |
E889138
|
entity |
| Predicate | currentReputation |
P60235
|
FINISHED |
| Object | obscure heritage grape |
—
|
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: obscure heritage grape | Statement: [Beaunoir, currentReputation, obscure heritage grape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentReputation Context triple: [Beaunoir, currentReputation, obscure heritage grape]
-
A.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
B.
liveReputation
chosen
Indicates a dynamic, continuously updated assessment of an entity’s standing, trustworthiness, or performance based on recent or real-time information.
-
C.
providesReputationWith
Indicates that one entity grants or assigns a reputation value, score, or status to another entity.
-
D.
crowdReputation
Indicates the collective opinion or perceived standing of an entity as judged by a group or general audience.
-
E.
checkpointReputation
Indicates that an entity’s reputation or trust level is evaluated, recorded, or updated at a specific checkpoint in a process or timeline.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 1, 2026, 2:04 a.m.