Triple
T22499104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISRG Root X1 |
E556220
|
entity |
| Predicate | subjectKeyIdentifier |
P108636
|
FINISHED |
| Object | C4A7B1A47B2C71F0A3E1D9D6D1E5B1B8 |
—
|
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: C4A7B1A47B2C71F0A3E1D9D6D1E5B1B8 | Statement: [ISRG Root X1, subjectKeyIdentifier, C4A7B1A47B2C71F0A3E1D9D6D1E5B1B8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectKeyIdentifier Context triple: [ISRG Root X1, subjectKeyIdentifier, C4A7B1A47B2C71F0A3E1D9D6D1E5B1B8]
-
A.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
-
B.
subjectKey
chosen
Indicates that the subject serves as a unique key or identifier used to reference or distinguish an entity in a relationship or dataset.
-
C.
signatureSubject
Indicates that an entity serves as the subject or principal party associated with a given signature.
-
D.
isKeyInterchangeFor
Indicates that one location or facility serves as a primary transfer point connecting major routes, lines, or modes of transport for another.
-
E.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
- 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_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. |
Created at: April 16, 2026, 8:50 p.m.