Triple
T32090621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fins Bois (Cognac cru) |
E819580
|
entity |
| Predicate | qualityProfile |
P156741
|
FINISHED |
| Object | round |
—
|
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: round | Statement: [Fins Bois (Cognac cru), qualityProfile, round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualityProfile Context triple: [Fins Bois (Cognac cru), qualityProfile, round]
-
A.
sonarSuite
Indicates that one entity is a sonar-related software suite or collection of sonar tools associated with another entity.
-
B.
qualityScheme
chosen
Indicates that an entity is associated with a particular quality assurance or quality classification scheme that defines how its quality is evaluated or certified.
-
C.
programmingCharacteristic
Indicates a relationship where an entity possesses or exhibits a particular property, trait, or quality specifically related to programming.
-
D.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
E.
engineeringReputation
Indicates the perceived quality, credibility, or esteem of an entity’s engineering capabilities or output as judged by others.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:25 a.m.