Triple
T6910535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rdfs:ContainerMembershipProperty |
E159919
|
entity |
| Predicate | rdf:type |
P29259
|
FINISHED |
| Object | rdfs:Class |
—
|
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: rdfs:Class | Statement: [rdfs:ContainerMembershipProperty, rdf:type, rdfs:Class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rdf:type Context triple: [rdfs:ContainerMembershipProperty, rdf:type, rdfs:Class]
-
A.
typeOfNamedThing
chosen
Indicates that one entity is the specific type or category to which the named thing belongs.
-
B.
protégéOf
Indicates that one entity is mentored, trained, or guided in their development by another, more experienced entity.
-
C.
conceptualRole
Indicates the functional or semantic role that one concept plays in relation to another within a conceptual structure or system.
-
D.
termType
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
E.
ontologyId
Indicates that there is an association between an entity and a specific ontology identifier that formally defines or classifies it within an ontology.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9c00e948190b103a2b2a2738bb1 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.