Triple
T22499096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISRG Root X1 |
E556220
|
entity |
| Predicate | notBefore |
P70965
|
FINISHED |
| Object | 2015-06-04T11:04:38Z |
—
|
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: 2015-06-04T11:04:38Z | Statement: [ISRG Root X1, notBefore, 2015-06-04T11:04:38Z]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notBefore Context triple: [ISRG Root X1, notBefore, 2015-06-04T11:04:38Z]
-
A.
notEarlierThan
chosen
Indicates that one event, time, or state does not occur before another, i.e., it is simultaneous with or later than the referenced point.
-
B.
grantedAfter
Indicates that one entity is granted or conferred only after another specified event, condition, or action has occurred.
-
C.
nonceRequirement
Indicates that a unique, one-time-use value (nonce) is required to be present or validated as part of the interaction or transaction between entities.
-
D.
releasedBefore
Indicates that one entity was released at an earlier time or date than another entity.
-
E.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
- 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.