Triple
T22499127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISRG Root X1 |
E556220
|
entity |
| Predicate | governingCP |
P148460
|
FINISHED |
| Object | ISRG Certificate Policy |
—
|
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: ISRG Certificate Policy | Statement: [ISRG Root X1, governingCP, ISRG Certificate Policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingCP Context triple: [ISRG Root X1, governingCP, ISRG Certificate Policy]
-
A.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
B.
governingOffice
Indicates the official position or office through which an entity exercises governing authority over a jurisdiction or organization.
-
C.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
D.
governingUnion
Indicates that one political or administrative entity serves as the primary governing authority over a union or collective of entities.
-
E.
holderGovernment
Indicates that a government entity serves as the official holder, custodian, or controlling authority over another entity.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb3deb88190874230ae06a352d6 |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:50 p.m.