Triple

T25372040
Position Surface form Disambiguated ID Type / Status
Subject 9P network protocol E632955 entity
Predicate operatesOnAbstraction P134875 FINISHED
Object file 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: file | Statement: [9P network protocol, operatesOnAbstraction, file]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatesOnAbstraction
Context triple: [9P network protocol, operatesOnAbstraction, file]
  • A. usesAbstraction chosen
    Indicates that one entity employs or relies on an abstract representation or interface of another entity rather than interacting with its concrete implementation directly.
  • B. providesAbstraction
    Indicates that one entity offers a higher-level, simplified interface or conceptual layer that hides the underlying complexity of another entity.
  • C. operatesOnPropertyOf
    Indicates that an action or process is applied specifically to a property or attribute of an entity, rather than to the entity itself.
  • D. definesOperationOn
    Indicates that one entity specifies or establishes the operation that is applied to another entity.
  • E. operatesOnProperty
    Indicates that one entity performs an action or has an effect specifically targeting a particular property or attribute of another entity.
  • 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_69e75a90c0dc819092f928b6ea0ecc72 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc53f4f881908dcc698687bbb64d completed May 3, 2026, 7:42 a.m.
Created at: April 21, 2026, 1:38 p.m.