Triple
T6910533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rdfs:ContainerMembershipProperty |
E159919
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rdfs:Class |
C2887
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: rdfs:Class Context triple: [rdfs:ContainerMembershipProperty, instanceOf, rdfs:Class]
-
A.
canonical classification
Canonical classification is a standardized method of organizing entities into universally recognized categories based on their essential, defining characteristics.
-
B.
classification board
A classification board is an authoritative body or panel that evaluates and assigns categories, ratings, or classifications to items such as media, products, or information based on defined criteria and standards.
-
C.
ontology
An ontology is a structured conceptual model that defines the entities, relationships, and rules within a specific domain to enable shared understanding and reasoning.
-
D.
Web ontology language
chosen
A web ontology language is a formal language designed for representing rich, machine-interpretable knowledge about concepts, relationships, and constraints on the web to enable automated reasoning and interoperability.
-
E.
taxonomicRank
A taxonomicRank is a level in the hierarchical classification system of organisms (such as species, genus, family, order, class, phylum, kingdom, or domain) that groups entities based on shared characteristics and evolutionary relationships.
- F. None of above.
Provenance (1 batch)
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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:25 p.m.