Triple
T31959287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veltha |
E815989
|
entity |
| Predicate | certaintyOfAttributes |
P36359
|
FINISHED |
| Object | low to moderate |
—
|
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: low to moderate | Statement: [Veltha, certaintyOfAttributes, low to moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certaintyOfAttributes Context triple: [Veltha, certaintyOfAttributes, low to moderate]
-
A.
hasCertainty
chosen
Indicates that a statement, belief, or relationship is associated with a specific level or degree of confidence or surety.
-
B.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
C.
confidenceLevel
Indicates the degree of certainty or assurance associated with a particular claim, decision, or outcome.
-
D.
certaintyOfReconstruction
Indicates the degree of confidence or reliability in how accurately something has been reconstructed from incomplete or indirect information.
-
E.
perceivedAttribute
Indicates that one entity recognizes, interprets, or assigns a particular attribute or quality to 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2b1de00819083a9d5654452e4cd |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:08 a.m.