Triple
T30315626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Root CA |
E771047
|
entity |
| Predicate | certificateStandard |
P169395
|
FINISHED |
| Object | X.509 |
—
|
NE NERFINISHED |
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: X.509 | Statement: [Apple Root CA, certificateStandard, X.509]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certificateStandard Context triple: [Apple Root CA, certificateStandard, X.509]
-
A.
certificateType
Indicates the specific kind or category of certificate associated with an entity or relationship.
-
B.
certificateRating
Indicates the quality or approval level assigned to a certificate, typically reflecting its trustworthiness or compliance with certain standards.
-
C.
certificateGrantedBy
Indicates that a certificate was issued or formally granted by a specific authority or organization to another entity.
-
D.
certificateTypesInclude
Indicates that the set of certificate types associated with one entity includes (i.e., contains as members) the certificate types specified by another entity.
-
E.
certificate
Indicates that an entity has been formally recognized or authorized through an official certificate associated with another entity or qualification.
- F. None of above. chosen
Provenance (4 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68193b2b08190a00f08dbba490563 |
completed | May 2, 2026, 10:58 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:51 p.m.