Triple

T27373154
Position Surface form Disambiguated ID Type / Status
Subject Thomas Fuchs E690383 entity
Predicate softwareLibraryDeveloped P115831 FINISHED
Object script.aculo.us 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: script.aculo.us | Statement: [Thomas Fuchs, softwareLibraryDeveloped, script.aculo.us]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: softwareLibraryDeveloped
Context triple: [Thomas Fuchs, softwareLibraryDeveloped, script.aculo.us]
  • A. softwareLibraryCreated chosen
    Indicates that an entity (typically a person or organization) is responsible for creating a particular software library.
  • B. developedSoftware
    Indicates that one entity created, programmed, or significantly contributed to the creation of a particular software system or application for another entity or purpose.
  • C. softwareLibrary
    Indicates that one entity is a software library that provides code, functionality, or services used by another entity.
  • D. scriptDevelopedFor
    Indicates that a script was specifically created or developed for use by, or in the context of, a particular entity or purpose.
  • E. developedWith
    Indicates that something was created, built, or produced using a specified tool, technology, method, or collaborator.
  • 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_69ef51ff826081909e42c8e2bfb97941 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f6383625cc8190aa223d8ef655743c completed May 2, 2026, 5:45 p.m.
PD Predicate disambiguation batch_69f63709e4848190b5cf322e06b23fb6 completed May 2, 2026, 5:40 p.m.
Created at: April 27, 2026, 12:19 p.m.