Triple
T27780767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco Certified DevNet Expert |
E699330
|
entity |
| Predicate | positionInTrack |
P86259
|
FINISHED |
| Object | highest-level DevNet certification |
—
|
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: highest-level DevNet certification | Statement: [Cisco Certified DevNet Expert, positionInTrack, highest-level DevNet certification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTrack Context triple: [Cisco Certified DevNet Expert, positionInTrack, highest-level DevNet certification]
-
A.
positionInTrackList
Indicates the specific ordered place an item occupies within a track list.
-
B.
positionOnRecord
chosen
Indicates the specific place or rank an item occupies within an ordered record or listing.
-
C.
positionInTrain
Indicates the relative location or ordering of an entity within the sequence of cars or sections that make up a train.
-
D.
positionOnRemix
Indicates the specific role or placement an entity has within a remix version of a work or composition.
-
E.
positionAt
Indicates that one entity is located at, or occupies, a specific spatial position relative to another entity or reference frame.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 27, 2026, 5:09 p.m.