Triple
T8494810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPCE |
E201070
|
entity |
| Predicate | hasVolatilityCharacteristic |
P48131
|
FINISHED |
| Object | high price volatility |
—
|
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: high price volatility | Statement: [SPCE, hasVolatilityCharacteristic, high price volatility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolatilityCharacteristic Context triple: [SPCE, hasVolatilityCharacteristic, high price volatility]
-
A.
hasLiquidityCharacteristic
Indicates that one entity possesses or is associated with a particular liquidity-related property or feature in relation to another entity.
-
B.
hasVariability
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
-
C.
volatility
chosen
Indicates that the degree of variability or instability in the related entity’s value, state, or behavior is being characterized.
-
D.
hasSafetyCharacteristic
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
-
E.
hasBankCharacteristic
Indicates that a bank possesses a particular attribute, feature, or quality.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57c01f881908cb77c8c834ac08d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.