Triple
T3900370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebRanger Program |
E90472
|
entity |
| Predicate | hasBadgeSystem |
P52752
|
FINISHED |
| Object | digital badges |
—
|
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: digital badges | Statement: [WebRanger Program, hasBadgeSystem, digital badges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBadgeSystem Context triple: [WebRanger Program, hasBadgeSystem, digital badges]
-
A.
hasExerciseRewardSystem
Indicates that an entity implements or is associated with a system that provides rewards or incentives for performing exercise or physical activity.
-
B.
badge
Indicates that one entity confers, displays, or is associated with a symbolic mark or emblem representing status, achievement, role, or affiliation in relation to another entity.
-
C.
hasTrophyStatus
Indicates that an entity possesses a particular trophy-related status or classification.
-
D.
qualificationBadge
Indicates that an entity has been awarded or holds a specific qualification badge signifying a certified skill, status, or achievement.
-
E.
hasAwardLevel
Indicates that an entity possesses or has been assigned a specific level, tier, or rank within an award or recognition system.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef1aada308190821a3dfa6af170b3 |
completed | March 9, 2026, 4:13 p.m. |
Created at: March 9, 2026, 3:21 p.m.