Triple

T1975861
Position Surface form Disambiguated ID Type / Status
Subject CREST E42909 entity
Predicate supportsMarket P32995 FINISHED
Object AIM E223465 NE 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: AIM | Statement: [CREST, supportsMarket, AIM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AIM
Context triple: [CREST, supportsMarket, AIM]
  • A. AIM
    AIM is the commonly used acronym for AOL Instant Messenger, a pioneering early internet instant messaging service.
  • B. AIM
    AIM is a global initiative focused on mobilizing coordinated actions and investments to eradicate malaria.
  • C. AIM chosen
    AIM is the London Stock Exchange’s market for smaller, growing companies that offers more flexible regulatory requirements than the Main Market.
  • D. AIM alliance
    The AIM alliance was a 1990s partnership between Apple, IBM, and Motorola formed to develop and promote the PowerPC microprocessor architecture as an alternative to Intel’s x86.
  • E. AIM securities
    AIM securities are shares and other financial instruments traded on the London Stock Exchange’s Alternative Investment Market, a sub-market designed for smaller, growing companies with lighter regulatory requirements.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a8871289048190b00b0d7744b7b2b1 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb7c698748190a10da0901952df07 completed March 7, 2026, 5:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae30467f2c8190adc3e619396c0f08 completed March 9, 2026, 2:28 a.m.
Created at: March 4, 2026, 7:36 p.m.