Triple

T3716945
Position Surface form Disambiguated ID Type / Status
Subject FTSE MIB E81552 entity
Predicate liquidityRequirement P25265 FINISHED
Object minimum trading volume for constituents 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: minimum trading volume for constituents | Statement: [FTSE MIB, liquidityRequirement, minimum trading volume for constituents]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: liquidityRequirement
Context triple: [FTSE MIB, liquidityRequirement, minimum trading volume for constituents]
  • A. marginRequirement
    Indicates the minimum amount of collateral or equity that must be maintained to support a position or transaction, typically expressed as a percentage of the position’s value.
  • B. requiresMinimumCapital
    Indicates that one entity can only proceed, be valid, or be permitted if a specified minimum amount of capital is available or provided.
  • C. hasLiquidityCharacteristic chosen
    Indicates that one entity possesses or is associated with a particular liquidity-related property or feature in relation to another entity.
  • D. collateralRequired
    Indicates that a party must provide collateral as a condition or security for an obligation, transaction, or agreement.
  • E. beneficiaryRequirement
    Indicates that one entity has a requirement specifying who or what must be the beneficiary of a particular action, service, or resource.
  • 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_69ad8b1a81588190b3f27a5483bb610e completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adc9d087c881909f6d2ec6e518fb02 completed March 8, 2026, 7:11 p.m.
PD Predicate disambiguation batch_69adc0436e508190909ec4a3e8443aef completed March 8, 2026, 6:30 p.m.
Created at: March 8, 2026, 3:33 p.m.