Triple
T1600558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco Certified Internetwork Expert |
E34380
|
entity |
| Predicate | renewalMethod |
P30610
|
FINISHED |
| Object | recertification exam |
—
|
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: recertification exam | Statement: [Cisco Certified Internetwork Expert, renewalMethod, recertification exam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renewalMethod Context triple: [Cisco Certified Internetwork Expert, renewalMethod, recertification exam]
-
A.
renewalTerm
Indicates the length or conditions of time for which an agreement, contract, or subscription is extended beyond its initial term.
-
B.
renewalPattern
Indicates the recurring schedule or frequency with which something is renewed or repeated over time.
-
C.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
-
D.
isRenewable
Indicates that a resource or energy source can be naturally replenished or regenerated within a human-relevant timescale.
-
E.
recoveryMethod
Indicates the method or process by which something is restored, retrieved, or brought back to a previous or functional state.
- 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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a95aada3f881909053363c01de8b57 |
completed | March 5, 2026, 10:29 a.m. |
Created at: March 4, 2026, 7:28 p.m.