Triple

T21423675
Position Surface form Disambiguated ID Type / Status
Subject Brian Moriarty E528498 entity
Predicate wrote P2831 FINISHED
Object Loom NE NERFINISHED

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: Loom | Statement: [Brian Moriarty, wrote, Loom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Loom
Context triple: [Brian Moriarty, wrote, Loom]
  • A. Loom chosen
    Loom is a 1990 fantasy point-and-click adventure game by Lucasfilm Games, notable for its unique musical spellcasting interface and story-driven design.
  • B. Loomstate
    Loomstate is a sustainable fashion brand known for its use of organic materials and environmentally responsible production practices.
  • C. Weave
    Weave was the original name of Mozilla’s cloud-based synchronization service that later became known as Firefox Sync.
  • D. Weave
    Weave is Google's Internet of Things (IoT) communication platform designed to let smart devices easily discover, connect, and work together across different ecosystems.
  • E. Weave
    The Weave is the fundamental arcane fabric of the Forgotten Realms through which all spellcasting and magical effects are channeled and shaped.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c455f3688190810bc96365791b0f completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee8139ce848190b812d6d07f1bdef8 completed April 26, 2026, 9:18 p.m.
Created at: April 16, 2026, 5:48 p.m.