Triple

T4654910
Position Surface form Disambiguated ID Type / Status
Subject Avro E102384 entity
Predicate schemaDefinitionFormat P29507 FINISHED
Object JSON E39004 NE FINISHED

How this triple was built (3 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: JSON | Statement: [Avro, schemaDefinitionFormat, JSON]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: JSON
Context triple: [Avro, schemaDefinitionFormat, JSON]
  • A. JSON chosen
    JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format widely used for transmitting structured data in web APIs and configuration files.
  • B. JSON5
    JSON5 is an extension of the JSON data format that adds more human-friendly features like comments, trailing commas, and unquoted object keys while remaining largely compatible with standard JSON.
  • C. JSON API
    JSON API is a standardized specification for building JSON-based RESTful APIs that defines how clients should request and modify resources in a consistent, structured format.
  • D. Jakarta JSON Processing
    Jakarta JSON Processing is a Jakarta EE specification that defines a standard API for parsing, generating, transforming, and querying JSON data in Java applications.
  • E. JSONiq
    JSONiq is a query and processing language designed specifically for JSON data, extending concepts from XQuery to work with hierarchical and semi-structured information.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: schemaDefinitionFormat
Context triple: [Avro, schemaDefinitionFormat, JSON]
  • A. definitionType
    Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
  • B. strongFormDefinition
    Indicates that one entity provides a rigorous, fully detailed (strong form) definition of another entity or concept.
  • C. formalismType chosen
    Indicates the specific formal system or representational framework in which something (such as a theory, model, or specification) is expressed.
  • D. standardFormulation
    Indicates that something is expressed or represented in a conventional, officially accepted, or commonly used form or version.
  • E. logicalForm
    Indicates a relationship where an expression is associated with its structured, formal logical representation.
  • F. None of above.

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_69bd43d823288190952279faa0d1d066 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd6317ba70819089145766d3462e57 completed March 20, 2026, 3:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdfaef125c819097d79f25608302dc completed March 21, 2026, 1:57 a.m.
PD Predicate disambiguation batch_69bd62126b0c81909ba3f21b21e30d54 completed March 20, 2026, 3:04 p.m.
Created at: March 20, 2026, 1:14 p.m.