Triple

T32481284
Position Surface form Disambiguated ID Type / Status
Subject Linux kernel coding style E830115 entity
Predicate previouslyDocumentedIn P33255 FINISHED
Object Documentation/CodingStyle LITERAL 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: Documentation/CodingStyle | Statement: [Linux kernel coding style, previouslyDocumentedIn, Documentation/CodingStyle]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: previouslyDocumentedIn
Context triple: [Linux kernel coding style, previouslyDocumentedIn, Documentation/CodingStyle]
  • A. previouslyIn
    Indicates that an entity was located in, part of, or associated with another entity at some earlier time, but is not necessarily so now.
  • B. previouslyDefinedIn chosen
    Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
  • C. previouslyCoveredBy
    Indicates that something was earlier protected, enclosed, or overlaid by another object or material, but is no longer in that state.
  • D. legacyDocumentedBy
    Indicates that information about a legacy item or concept is recorded or described in a specific documenting source.
  • E. previouslyLocatedIn
    Indicates that an entity was located in a particular place or region at some time in the past, but is not necessarily located there now.
  • 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_69f3491ff3b48190b50a7fa00bb05b1f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69febce5877c8190a5e000ef5331ec88 completed May 9, 2026, 4:49 a.m.
PD Predicate disambiguation batch_69febad1cd588190abc7686bcb39a371 completed May 9, 2026, 4:40 a.m.
Created at: May 1, 2026, 12:58 a.m.