Triple
T34569444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petit Meslier |
E887582
|
entity |
| Predicate | statusInChampagne |
P127
|
FINISHED |
| Object | authorized but minor 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: authorized but minor variety | Statement: [Petit Meslier, statusInChampagne, authorized but minor variety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInChampagne Context triple: [Petit Meslier, statusInChampagne, authorized but minor variety]
-
A.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
B.
statusInFinale
Indicates the role, condition, or outcome an entity has specifically in the final episode or concluding segment of a series or event.
-
C.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
D.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
challengerStatus
Indicates the role or condition of an entity as a challenger in a competitive or adversarial 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: May 1, 2026, 2:02 a.m.