Triple

T27584894
Position Surface form Disambiguated ID Type / Status
Subject Meta Object Facility E699667 entity
Predicate layerInArchitecture P36580 FINISHED
Object meta-metamodel layer 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: meta-metamodel layer | Statement: [Meta Object Facility, layerInArchitecture, meta-metamodel layer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: layerInArchitecture
Context triple: [Meta Object Facility, layerInArchitecture, meta-metamodel layer]
  • A. layerOf chosen
    Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
  • B. frameworkLayer
    Indicates a relationship where one framework is organized within, built upon, or conceptually assigned to a particular architectural or conceptual layer.
  • C. layerStructure
    Indicates a relationship where one entity is organized in or assigned to a specific layer or hierarchical level within a structured system.
  • D. layerType
    Indicates the specific kind or category of layer that an entity belongs to or is classified as.
  • E. OSIModelLayer
    Indicates the specific layer within the OSI (Open Systems Interconnection) model at which a networking function, protocol, or interaction operates.
  • 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_69ef6a4cb8b881909b3a8d630fd89df2 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f630197e588190aa67eea748797157 completed May 2, 2026, 5:10 p.m.
PD Predicate disambiguation batch_69f62c1921008190a62675a31f66a875 completed May 2, 2026, 4:53 p.m.
Created at: April 27, 2026, 2:04 p.m.