Triple

T9028932
Position Surface form Disambiguated ID Type / Status
Subject FTSE All-World Index E216118 entity
Predicate securityCapitalizationCoverage P85966 FINISHED
Object large-cap stocks 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: large-cap stocks | Statement: [FTSE All-World Index, securityCapitalizationCoverage, large-cap stocks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: securityCapitalizationCoverage
Context triple: [FTSE All-World Index, securityCapitalizationCoverage, large-cap stocks]
  • A. securityGuarantee
    Indicates a commitment by one party to protect or defend another party against specified threats or risks.
  • B. securityStatus
    Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
  • C. helpedSecure
    Indicates that one entity contributed to obtaining, protecting, or ensuring the safety or stability of another entity or outcome.
  • D. securityLevelDetail
    Indicates the specific classification or degree of security associated with an entity, often including nuanced or descriptive information about its protection level.
  • E. securityCodename
    Indicates that an entity is assigned a specific codename used for security, confidentiality, or protective identification purposes.
  • F. None of above. chosen

Provenance (4 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_69ca83a5fa88819088144801b4dd7245 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6a9bcb508190b58751f1772407d4 completed April 1, 2026, 12:45 a.m.
PD Predicate disambiguation batch_69cc5ee132f08190940749c7c522e4c1 completed March 31, 2026, 11:55 p.m.
PDg Predicate description generation batch_69cc5f887108819096d45a186fc137b3 completed March 31, 2026, 11:58 p.m.
Created at: March 30, 2026, 7:08 p.m.