Triple

T12514653
Position Surface form Disambiguated ID Type / Status
Subject printf E299164 entity
Predicate introducedIn P513 FINISHED
Object POSIX.1-1990 E183310 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: POSIX.1-1990 | Statement: [printf, introducedIn, POSIX.1-1990]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: POSIX.1-1990
Context triple: [printf, introducedIn, POSIX.1-1990]
  • A. POSIX chosen
    POSIX is a family of standardized operating system interfaces and utilities that ensure compatibility and portability among Unix-like systems and applications.
  • B. POSIX.1q
    POSIX.1q is the IEEE standard that defines Virtual LAN (VLAN) tagging for Ethernet networks, commonly known as IEEE 802.1Q.
  • C. ISO/IEC 9899
    ISO/IEC 9899 is the international standard that defines the C programming language’s syntax, semantics, and library.
  • D. UNIX 98
    UNIX 98 is a version of the Single UNIX Specification that standardized key operating system interfaces and behaviors for UNIX systems in the late 1990s.
  • E. Single UNIX Specification
    The Single UNIX Specification is an industry standard that defines the requirements and interfaces for operating systems to be branded and interoperable as UNIX.
  • 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_69d6ada5cdd48190860d9ce30aff69be completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9541e752c8190bf12d2b5a37b53df completed April 10, 2026, 7:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64bbba5fc819082a4171a5a77183a completed May 2, 2026, 7:08 p.m.
Created at: April 8, 2026, 9:57 p.m.